Skip to main content
Glama

search_calls

Read-only

Search Gong calls with filters for date, participants, customer, topic, and duration. Narrow down relevant calls before retrieving summaries or transcripts.

Instructions

Search Gong calls with rich filters. The primary tool for narrowing down calls before drilling in with get_call_summary or get_call_transcript.

Supported filters:

  • When: fromDateTime, toDateTime (ISO 8601). Always prefer a date range — unbounded queries pull every call in the workspace.

  • Who hosted: primaryUserIds, primaryUserEmails, excludePrimaryUserIds.

  • Who participated (host OR attendee OR invitee): participantUserIds, participantEmails, excludeParticipantUserIds, excludeParticipantEmails.

  • Customer/topic: customerName (CRM account name, email domain, or title substring), titleContains, trackers (see note below).

  • Metadata: scope (External/Internal), direction, system (Zoom/Meet/…), language (eng/jpn/…), minDuration and maxDuration in seconds.

  • Output shape: include (array of keyPoints, trackers, highlights, speakers, comments, context, outline, media). Parties + brief + topics are always returned.

Behavior:

  • Auto-paginates up to ~5000 calls. If a user asks for a broad question, guide them to narrow with a date range, scope, minDuration, or customerName first.

  • trackers filter does case-insensitive substring match on tracker names. Names are workspace-specific — call get_trackers first to see what's configured before guessing.

  • When the rich output would exceed the output cap, the tool auto-falls back to a compact table showing all IDs/titles. Use get_call_summary on specific IDs to go deeper.

  • Filters compose with AND logic (primaryUserIds + customerName = hosted by user X on customer Y calls).

Usage pattern: narrow with search_calls → drill into specific calls with get_call_summary (AI summary) or get_call_transcript (exact quotes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoFilter by call scope: External (customer-facing), Internal (team), or Unknown.
systemNoFilter by conferencing system (e.g., "Zoom", "Google Meet"). Case-insensitive substring match.
callIdsNoFilter by specific call IDs. Array of numeric strings.
includeNoAdditional per-call data beyond the defaults (parties, brief, topics). Start lean and add fields as needed — each extra field multiplies response size by number of calls. Options: keyPoints (~5KB/call), trackers (~3KB/call, auto-added when trackers filter is used), highlights (~3KB/call), speakers (talk time, ~1KB/call), comments (varies), context (CRM links, ~1KB/call), outline (~80KB/call, AVOID unless you need full structure of one call), media (audio/video URLs).
languageNoFilter by language code (e.g., "eng", "jpn"). Case-insensitive exact match.
trackersNoFilter calls where at least one matching tracker fired (count > 0). Tracker names are matched case-insensitive substring and vary by workspace — call get_trackers first to discover what is configured.
directionNoFilter by call direction: Inbound, Outbound, Conference, or Unknown.
toDateTimeNoEnd date/time filter in ISO 8601 format (e.g., 2024-01-31T23:59:59Z). Strongly recommended alongside fromDateTime. Must be after fromDateTime if both specified.
maxDurationNoMaximum call duration in seconds.
minDurationNoMinimum call duration in seconds. Useful for filtering out no-shows or misfired meetings.
workspaceIdNoFilter calls by workspace ID (numeric string up to 20 digits)
customerNameNoFilter by customer/account name (case-insensitive substring match). Searches CRM account name, external participant email domains, and call titles.
fromDateTimeNoStart date/time filter in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Strongly recommended — without a date range, the tool pulls every call in the workspace. Must be before toDateTime if both specified.
titleContainsNoFilter calls whose title contains this substring (case-insensitive).
primaryUserIdsNoFilter by primary user IDs (call hosts only, server-side). Use participantUserIds to find calls where a user was any participant.
participantEmailsNoFilter by participant email addresses (case-insensitive). Matches calls where any participant has a matching email.
primaryUserEmailsNoFilter by host email (case-insensitive). Alternative to primaryUserIds when you have emails instead of user IDs.
participantUserIdsNoFilter by participant user IDs. Matches calls where any participant (host, attendee, or invitee) has a matching Gong user ID. Requires a date range for optimal performance.
excludePrimaryUserIdsNoExclude calls hosted by these user IDs.
excludeParticipantEmailsNoExclude calls where any participant has a matching email (case-insensitive).
excludeParticipantUserIdsNoExclude calls where any participant has a matching user ID.
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description reveals auto-pagination up to ~5000 calls, automatic fallback to a compact table when output exceeds caps, AND-composition of filters, case-insensitive tracker matching, and performance implications of the include fields. This is rich behavioral disclosure.

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 long but appropriately structured: a one-line purpose, grouped filter list, behavioral notes, and a usage pattern. Headings and bullets make it scannable, and every section adds actionable guidance beyond the schema.

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?

Given the tool's complexity (21 parameters, no output schema), the description covers return shape (always-returned fields, output size behavior), pagination limits, fallback behavior, and performance guidance. It gives the agent everything needed to decide when and how to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by grouping filters (e.g., 'Who hosted', 'Who participated'), warning about unbounded date ranges, recommending get_trackers first, and providing size estimates for include options (e.g., outline ~80KB/call). These are practical semantic additions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Search Gong calls with rich filters' and identifies itself as 'the primary tool for narrowing down calls before drilling in with get_call_summary or get_call_transcript.' This clearly distinguishes it from siblings like list_calls and the account/opportunity-specific search tools.

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?

It explicitly frames the tool as the primary narrowing step and names get_call_summary and get_call_transcript as follow-up alternatives. It does not explicitly exclude related search tools like search_calls_by_account, but it gives strong contextual guidance for when to use this tool.

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/JustinBeckwith/gongio-mcp'

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