Skip to main content
Glama
Gong MCP

Gong MCP

by tadnir

search_calls

Find Gong calls newest first by date range, title, account, deal, contact email or participant. Returns totals plus each call's id, time, duration, owner, participants, account, deal, topics and brief.

Instructions

Find calls, newest first: by date range, title, account, deal, external contact email or company participants. Returns the total and each call's id, title, start time, duration, owner, participants, account and deal, topics and Gong's brief.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_calls"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default: today.
fromNoFirst day, YYYY-MM-DD. Default: 30 days ago.
limitNoHow many calls, 1-100. Default 25.
titleNoWords in the call's title.
offsetNoSkip this many, for the next page.
accountNoAccount (company) name, as in the CRM.
dealCrmIdNoThe deal's (opportunity's) CRM id, from list_deals.
accountCrmIdNoThe account's CRM id, from list_accounts.
contactEmailNoEmail of an external participant.
participantIdsNoGong user ids of company participants, from find_people.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses ordering ("newest first") and the returned fields, but says nothing about read-only semantics, permission/auth requirements, rate limits, or pagination behavior beyond what offset/limit in the schema imply.

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?

Two sentences, front-loaded with the verb and sort order, then the return shape. No redundant restatement of the tool name, and the field enumeration earns its place because no output schema exists.

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 10-parameter, zero-required search tool with no output schema and no annotations, the description covers both the search axes and the response contents, which is what an agent needs to call it. It could add a note on default pagination and on the read-only nature, but nothing essential 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 description coverage is 100%, so every parameter is already documented, including cross-tool hints like "from list_deals" and "from find_people." The description groups the filter categories (date range, title, account, deal, contact email, participant ids), which adds light orientation but no syntax or format detail beyond the schema.

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?

Opens with a specific verb+resource ("Find calls") and enumerates the filterable dimensions, which lets an agent distinguish a list/search operation from get_call. It stops short of naming a sibling or stating that it returns a collection rather than a single call, so the differentiation is implied 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?

The filter list implies when this tool is appropriate (broad lookups by date, account, deal, or participant), but there is no explicit when-to-use or when-not guidance, no mention of get_call for single-call retrieval, and no prerequisite notes. Usage must be inferred from the available filters.

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