Skip to main content
Glama
Sign In
Gong-MCP

Gong-MCP

by alroy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Call Transcripts

search_calls
Read-only

Find specific keywords in Gong call transcripts within a chosen date range and get matching sentences with context. Ideal for quickly locating discussions or topics across calls.

Instructions

Search Gong call transcripts for keywords within a date range. Returns matching sentences with call context (case-insensitive substring match). Caps the number of calls scanned per invocation; narrow the date range if there are more.

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

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeywords to search for in transcripts
maxCallsNoMax calls to scan (default 50, hard cap 200)
toDateTimeYesEnd of date range (ISO-8601)
fromDateTimeYesStart of date range (ISO-8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description adds real behavioral value: case-insensitive substring matching, the return shape (matching sentences with call context), and the call-scan cap per invocation with remediation advice. It does not mention pagination handling or permission requirements, so it falls short of a 5.

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 tight sentences, front-loaded with the core action, then behavior, then the operational caveat. No filler and every sentence earns its place.

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?

Although no output schema exists, the description covers the return value (matching sentences with call context) and the scan-cap constraint, which are the main things an agent needs. Minor gaps remain around pagination or result limits, but the definition is substantially complete.

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% with each parameter documented (keywords, ISO-8601 dates, maxCalls default 50 / hard cap 200). The description adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 (search) and resource (Gong call transcripts) with scope (keywords, date range). It is clearly distinguishable from list_calls/get_transcripts in practice, but it never names a sibling or explicitly contrasts its purpose, so it stops short of full sibling differentiation.

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?

Gives one operational guideline - narrow the date range if more calls exist than the scan cap - which implies usage context but does not state when to choose this over get_transcripts or list_calls. Usage is inferred rather than spelled out.

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