Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

get_call

Retrieve a single Gong call's title, time, duration, participants, account, deal, topics, trackers, and analysis using its call ID.

Instructions

One call's details: title, time, duration, participants (company and external), the account and deal, topics, trackers and other analysis Gong shows on the call page.

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"
  }
}

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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the payload contents (participants, account, deal, topics, trackers, analysis), which is useful, but says nothing about access restrictions, permission requirements, or what happens when the id is invalid or the call is unavailable.

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 compact sentence that front-loads the resource and then lists the returned fields, with no filler. It is a fragment rather than a sentence, but nothing in it is wasted.

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

Completeness4/5

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

For a one-parameter lookup with no output schema, the enumeration of returned fields effectively substitutes for a return-value description. The main remaining gap is behavioral – no note on permissions or failure modes – which is minor for a straightforward read.

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% and there is a single required parameter, so the schema already explains that callId is a Gong call id obtained from search_calls. The description adds no further meaning about the parameter, which is acceptable at the baseline for fully covered schemas.

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 resource ('One call's details') and enumerates the fields returned — title, time, duration, participants, account, deal, topics, trackers, analysis. This makes its scope distinguishable from a transcript retrieval, but it never names a sibling tool, so differentiation is implicit rather than explicit.

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?

Usage is only implied: fetch the details of a single call by id. The description does add a workflow cue by pointing to search_calls as the source of the callId, but it gives no when-to-use vs. when-to-use-another-tool guidance and no exclusions.

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