Gong MCP Server
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_ACCESS_SECRET | Yes | Your Gong API access secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_callsB | List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration. |
| retrieve_transcriptsB | Retrieve transcripts for specified call IDs. Returns detailed transcripts including speaker IDs, topics, and timestamped sentences. |
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 2 tools
The two tools have clearly distinct purposes: list_calls retrieves metadata about calls, while retrieve_transcripts fetches detailed transcripts for specific calls. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.
Both tools follow a consistent verb_noun pattern (list_calls and retrieve_transcripts), using snake_case and clear action verbs. The naming is predictable and readable across the set.
With only two tools, the server feels thin for a Gong MCP server, which typically handles call-related operations. This limited set may not cover essential workflows like creating, updating, or deleting calls, or accessing other call metadata beyond listing and transcripts.
Inferring the domain as call management, there are significant gaps: no tools for creating, updating, or deleting calls, and missing operations like searching calls, accessing call recordings, or managing participants. This incomplete surface will likely cause agent failures in broader workflows.