Skip to main content
Glama
kenazk

Gong MCP Server

by kenazk

list_calls

Retrieve Gong call recordings and transcripts by listing calls with optional date range filtering to access details like participants, duration, and timestamps.

Instructions

List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromDateTimeNoStart date/time in ISO format (e.g. 2024-03-01T00:00:00Z)
toDateTimeNoEnd date/time in ISO format (e.g. 2024-03-31T23:59:59Z)

Implementation Reference

  • The execution handler for the 'list_calls' tool. It validates the input arguments using isGongListCallsArgs, calls the GongClient's listCalls method with the provided date range parameters, and returns the response as formatted JSON text.
    case "list_calls": {
      if (!isGongListCallsArgs(args)) {
        throw new Error("Invalid arguments for list_calls");
      }
      const { fromDateTime, toDateTime } = args;
      const response = await gongClient.listCalls(fromDateTime, toDateTime);
      return {
        content: [{ 
          type: "text", 
          text: JSON.stringify(response, null, 2)
        }],
        isError: false,
      };
    }
  • Tool definition for 'list_calls' including name, description, and inputSchema which defines the expected input parameters (fromDateTime and toDateTime as optional strings). This serves as the schema for the tool.
    const LIST_CALLS_TOOL: Tool = {
      name: "list_calls",
      description: "List Gong calls with optional date range filtering. Returns call details including ID, title, start/end times, participants, and duration.",
      inputSchema: {
        type: "object",
        properties: {
          fromDateTime: {
            type: "string",
            description: "Start date/time in ISO format (e.g. 2024-03-01T00:00:00Z)"
          },
          toDateTime: {
            type: "string",
            description: "End date/time in ISO format (e.g. 2024-03-31T23:59:59Z)"
          }
        }
      }
    };
  • src/index.ts:219-221 (registration)
    Registration of available tools via the ListToolsRequestSchema handler, which returns the list including LIST_CALLS_TOOL.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [LIST_CALLS_TOOL, RETRIEVE_TRANSCRIPTS_TOOL],
    }));
  • GongClient helper method that makes the authenticated API request to list calls with optional date filters.
    async listCalls(fromDateTime?: string, toDateTime?: string): Promise<GongListCallsResponse> {
      const params: GongListCallsArgs = {};
      if (fromDateTime) params.fromDateTime = fromDateTime;
      if (toDateTime) params.toDateTime = toDateTime;
    
      return this.request<GongListCallsResponse>('GET', '/calls', params);
    }
  • Type guard function for validating 'list_calls' arguments matching GongListCallsArgs interface.
    function isGongListCallsArgs(args: unknown): args is GongListCallsArgs {
      return (
        typeof args === "object" &&
        args !== null &&
        (!("fromDateTime" in args) || typeof (args as GongListCallsArgs).fromDateTime === "string") &&
        (!("toDateTime" in args) || typeof (args as GongListCallsArgs).toDateTime === "string")
      );
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns call details, but lacks information on permissions, rate limits, pagination, or error handling. This is inadequate for a tool with potential complexity in data retrieval.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, optional filtering, and return details. It is front-loaded and wastes no words, making it highly concise.

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?

Given no annotations and no output schema, the description partially compensates by listing return fields, but it lacks details on behavioral aspects like pagination or error handling. For a list tool with two parameters, it is minimally adequate but leaves gaps in operational context.

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 description mentions optional date range filtering, which aligns with the two parameters in the schema. Since schema description coverage is 100%, the description adds minimal value beyond what the schema already documents, meeting the baseline for high coverage.

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 clearly states the tool's purpose with a specific verb ('List') and resource ('Gong calls'), and mentions optional date range filtering. It distinguishes from the sibling 'retrieve_transcripts' by focusing on call metadata rather than transcripts, though not explicitly contrasted.

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 for retrieving call details with date filtering, but provides no explicit guidance on when to use this tool versus alternatives like 'retrieve_transcripts' or other potential tools. No exclusions or prerequisites are mentioned.

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/kenazk/gong-mcp'

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