Skip to main content
Glama
Sign In
Gong-MCP

Gong-MCP

by alroy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Gong Calls

list_calls
Read-only

List recorded Gong calls within a date range, returning call ID, title, start time, duration, direction, and URL. Use before retrieving transcripts.

Instructions

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.

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": {
      "fromDateTime": "<fromDateTime>",
      "toDateTime": "<toDateTime>"
    },
    "name": "list_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
toDateTimeYesEnd of date range in ISO-8601 format (e.g., '2026-03-28T23:59:59Z')
fromDateTimeYesStart of date range in ISO-8601 format (e.g., '2026-03-01T00:00:00Z')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, but the description adds real behavioral context beyond that: auto-pagination across Gong's cursor and the shape of the returned data. It stops short of disclosing pagination limits, rate limits, or date-range boundaries.

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?

Three short sentences, no redundancy, with the core purpose and date-range scope front-loaded. Every sentence carries distinct information: purpose, pagination behavior, return fields, and usage routing.

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

Completeness5/5

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

With no output schema, the description usefully enumerates the returned fields (ID, title, start time, duration, direction, URL) and explains pagination, which is exactly what an agent needs. Nothing essential for calling a two-parameter read tool is missing.

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 coverage is 100%, with both parameters documented including ISO-8601 format examples, so the schema already does the heavy lifting. The description only restates the date-range framing and adds no new meaning, so 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?

States a specific verb (List) and resource (calls recorded in Gong) scoped to a date range, which is clear. It does not explicitly distinguish itself from the sibling search_calls, so an agent must infer the boundary between listing and searching.

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

Usage Guidelines4/5

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

Gives a concrete usage context: 'Use this to find calls before retrieving transcripts,' routing the agent toward get_transcripts as a follow-up. It does not state when to prefer this over search_calls or when not to use it, so it lacks explicit alternative/exclusion guidance.

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

Deploy Server

Other Tools