Skip to main content
Glama

get_transcripts

Retrieve speaker-attributed, timestamped transcripts for specified Gong.io sales calls to analyze conversation data and review call details.

Instructions

Retrieve full transcripts for specified calls. Returns speaker-attributed, timestamped transcript text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callIdsYesArray of call IDs to retrieve transcripts for

Implementation Reference

  • Core handler function implementing the get_transcripts tool logic by calling the Gong API endpoint /v2/calls/transcript.
    async getTranscripts(callIds: string[]): Promise<TranscriptsResponse> {
    	const body = {
    		filter: {
    			callIds,
    		},
    	};
    	return this.request<TranscriptsResponse>('POST', '/calls/transcript', body);
    }
  • Input schema defining the parameters for the get_transcripts tool.
    inputSchema: {
      type: "object",
      properties: {
        callIds: {
          type: "array",
          items: { type: "string" },
          description: "Array of call IDs to retrieve transcripts for",
        },
      },
      required: ["callIds"],
    },
  • src/index.ts:85-100 (registration)
    Tool registration in the listTools handler, providing name, description, and schema.
    {
      name: "get_transcripts",
      description:
        "Retrieve full transcripts for specified calls. Returns speaker-attributed, timestamped transcript text.",
      inputSchema: {
        type: "object",
        properties: {
          callIds: {
            type: "array",
            items: { type: "string" },
            description: "Array of call IDs to retrieve transcripts for",
          },
        },
        required: ["callIds"],
      },
    },
  • MCP server tool execution handler (dispatcher) for get_transcripts, which calls the core GongClient implementation.
    case "get_transcripts": {
      const callIds = args?.callIds as string[];
      if (!callIds?.length) {
        throw new Error("callIds is required and must be a non-empty array");
      }
      const result = await gong.getTranscripts(callIds);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • TypeScript interface for the output response structure of getTranscripts.
    export interface TranscriptsResponse {
    	requestId: string;
    	records: {
    		cursor?: string;
    		totalRecords: number;
    		currentPageSize: number;
    		currentPageNumber: number;
    	};
    	callTranscripts: CallTranscript[];
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (speaker-attributed, timestamped transcript text), which is useful behavioral context. However, it lacks details on permissions, rate limits, error handling, or pagination, leaving gaps for a read operation.

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

Conciseness5/5

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

The description is two concise sentences with zero waste: the first states the purpose, and the second adds critical behavioral detail about the return format. It is front-loaded and efficiently structured.

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 read tool with no annotations and no output schema, the description provides basic purpose and return format, but lacks completeness in areas like error cases, authentication needs, or response structure details, which could aid the agent in correct invocation.

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?

Schema description coverage is 100%, so the schema already documents the callIds parameter fully. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the verb ('Retrieve') and resource ('full transcripts for specified calls'), and distinguishes from siblings by specifying it returns speaker-attributed, timestamped transcript text, unlike get_call_details (likely metadata) or list_calls (likely summaries).

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

Usage Guidelines3/5

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

The description implies usage when full transcripts are needed, but does not explicitly state when to use this tool versus alternatives like get_call_details or search_calls, nor provide exclusions or prerequisites for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JustinBeckwith/gongio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server