Gong-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GONG_ACCESS_KEY | Yes | Your Gong API access key | |
| GONG_SECRET_KEY | Yes | Your Gong API secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_callsA | List calls recorded in Gong within a date range. Auto-paginates across Gong's cursor. Returns call ID, title, start time, duration, direction, and URL. Use this to find calls before retrieving transcripts. |
| get_call_detailsA | Get detailed info about specific Gong calls including participants (name, email, title, internal vs external), topics, and trackers. Provide call IDs from list_calls. |
| get_transcriptsA | Retrieve full transcripts for Gong calls segmented by speaker with timestamps. Match speakerId against parties from get_call_details to identify who said what. |
| search_callsA | Search Gong call transcripts for keywords within a date range. Returns matching sentences with call context (case-insensitive substring match). Caps the number of calls scanned per invocation; narrow the date range if there are more. |
| get_usersA | List Gong users (company team members). Returns id, name, email, title. Use to map speaker IDs in transcripts to people. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing calls, getting call details, retrieving transcripts, searching transcripts, and listing users. Descriptions explicitly clarify boundaries, such as get_call_details vs get_transcripts vs search_calls.
Mostly consistent verb_noun pattern (list_calls, get_call_details, get_transcripts, search_calls, get_users), but 'get_call_details' adds '_details' while others are simple. Minor deviation but still predictable.
Five well-scoped tools that each cover a distinct aspect of Gong call data retrieval and user mapping. No redundancy or missing obvious operations.
Covers core read-only workflows: listing calls, getting details, transcripts, searching, and user listing. Missing write operations (e.g., create/update call notes) but likely out of scope for an MCP server focused on data access.