Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

get_call_transcript

Retrieve a specific Gong call's transcript by call ID, including what each speaker said and timestamps, to review conversation details.

Instructions

One call's transcript: what each speaker said, with timestamps.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "callId": "<callId>"
    },
    "name": "get_call_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
callIdYesThe call's Gong id, from search_calls (the number in a call page's ?id=).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden alone; it does disclose the shape of the returned content (per-speaker text with timestamps), which is the most valuable behavioral fact given there is no output schema. However, it says nothing about whether the call must have a recording, transcript availability, truncation or pagination, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the resource and its contents with no filler. It is efficient, though the omitted verb makes it read as a fragment rather than a fully formed instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with a fully documented schema, the description covers what comes back, which is what matters most absent an output schema. It still leaves gaps around transcript availability, size limits, and authentication that a caller may need to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single callId parameter is fully documented in the schema, including where to get it (search_calls, the ?id= in a call page URL). The description adds no meaning beyond that, but with 100% schema coverage and one parameter, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('One call's transcript') and describes its content (speaker utterances with timestamps), which clearly separates it from get_call's likely metadata output. The verb is only implied by the noun phrase, and no sibling is named explicitly, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use framing and no mention of alternatives such as get_call or search_calls, even though search_calls is named in the schema for obtaining a callId. An agent must infer that this tool is the choice when per-speaker text is needed rather than call metadata.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.