Who can use this: Tech admin
Available on: Any Gong plan
MCP server tools and related APIs consume Gong credits when they analyze calls and emails to generate AI insights.
Each request made by an external AI agent or API endpoint triggers analysis of Gong data. Credit usage depends on how much data is processed to generate the response.
MCP server tools and APIs use the same credit model.
APIs that use Gong credits
The following APIs consume Gong credits when generating AI insights:
ask-entity API: Used to answer questions about accounts and deals
get-brief API: Used to generate structured summaries known as briefs
MCP server tools map directly to these APIs:
ask_account and ask_deal use the ask-entity API
generate_brief uses the get-brief API
Credit consumption is based on the volume of calls and emails analyzed by these APIs.
Factors that impact credit usage
The following factors impact usage:
Time range: Longer time ranges increase the number of calls and emails analyzed
Prompt scope: Broad or open-ended prompts increase the volume of data processed
Request method: MCP and API requests consume the same number of credits
Repeated requests: Credits are consumed each time you call the MCP server or API endpoint, even if there is no change to the request
Designing briefs
The generate_brief tool and get-brief API can consume more credits than other MCP tools and APIs because a brief includes multiple sections, each contributing to the total credit usage.
Where possible, use smart trackers in brief sections. Smart tracker-based sections don’t consume additional credits, as the data has already been analyzed.
The number and type of sections directly impact usage. Briefs with more open-ended sections consume more credits.
To reduce credit usage, limit the number of open-ended sections and use more focused sections where possible.
Choosing between MCP server and Gong
Use MCP server tools or APIs when insights are required outside Gong or combined with external data.
Integrating external data: Combine Gong insights with CRM, marketing, or support systems
External workflows: Run workflows outside Gong without switching tools
Custom outputs: Generate flexible outputs such as summaries or reports
When to use Gong-native features
Use Gong when the workflow is fully supported within Gong.
Gong-only workflows: Account reviews, deal reviews, and standard analysis
Coaching and specialized analysis: Gong models provide more accurate insights for coaching scenarios
Raw data access: Use Gong APIs when raw data is required, as MCP returns only summarized insights
Managing credit usage
To control credit consumption when using MCP server tools and APIs, design prompts carefully.
Limit the time range
Clearly define how far back the external AI agent should analyze data.
❌ Too broad
“Give me a full summary of this account and everything discussed with the customer”
✅ Defines a clear time range
“What risks were mentioned for this account in the last 30 days?”
Use targeted prompts
Ask for specific insights instead of broad summaries.
❌ Unfocused request
“Can you summarize what’s happening with this deal?”
✅ Targets a specific insight
“What objections were raised in this deal in the last 14 days?”
Apply filters
Limit analysis to relevant data by specifying the correct account, deal, or time period.
❌ Too much data included
“Show all risks across all deals”
✅ Restricts the scope
“Show risks for this deal in the last 30 days”
Use MCP only when needed
Use MCP when insights are needed outside Gong or combined with external data.
❌ Unnecessary MCP usage
Using MCP to generate a deal summary that already exists in Gong
✅ Appropriate MCP usage
Using MCP to combine Gong insights with CRM or support data in an external workflow
Use Gong for Gong-native workflows
Use Gong when generating briefs or asking questions within Gong.
❌ Uses MCP for a Gong-native workflow
Using MCP or APIs to generate a brief or ask a question that can be done directly in Gong
✅ Uses Gong directly
Generating a brief or asking a question in the Gong UI, which does not consume MCP or API credits