search_calls is the entry point — it scopes results to what your authenticated user can see, supports a wide set of filters (date, rep, team, CRM fields, transcript content), and returns IDs that you can pass to get_call_details for a single call or to ask_attention for batch AI analysis.
Tools
search_calls
Scope:
mcp:read.Pagination
integer
Page number (starts from 1).
integer
Number of calls per page. Maximum: 50.
Date range
string
Show calls after this date. Format:
2024-01-01T00:00:00Z.string
Show calls before this date. Format:
2024-12-31T23:59:59Z.Owner & team
string
Filter by call owner email. Useful for admins/managers to view a specific rep’s calls. Sales reps already see their team’s calls by default.
string
Filter by call owner user ID. Alternative to
rep_email.string
Filter by team ID. Results are already scoped to your accessible teams based on your role.
Keyword & participants
string
Search calls by title keyword.
string
Filter by external participant email.
string
Search inside call transcripts for specific words or phrases. Returns calls where the transcript contains the search term, with matched snippets showing who said what.Compatibility:
transcript_search cannot be combined with crm_field_*, opportunity_id, participant_email, rep_email, rep_id, or title. It can be combined with from_date, to_date, team_id, and the hide_* filters. If you need both, run two searches and cross-reference the IDs.CRM filters
string
Filter by CRM opportunity/deal ID. The preferred way to find calls linked to a specific opportunity.
string
CRM entity code (e.g.
opportunity, account, contact). Required together with crm_field_field_name and crm_field_values.string
CRM field name to match (e.g.
StageName, Name). Required together with crm_field_entity_code and crm_field_values.array
Values to match for the CRM field (OR logic, max 10). Required together with
crm_field_entity_code and crm_field_field_name.Status filters
These default to safe values; only set them when the user explicitly asks.boolean
Exclude internal-only meetings.
boolean
Exclude calls that haven’t been analyzed.
boolean
Exclude calls that are still pending processing.
boolean
Exclude calls whose processing failed.
boolean
Exclude calls without a transcript. Defaults to
true — most assistants only need calls that have transcript data.Result enrichment
Optional flags that add detail to each result. Only set when the user has asked for that detail; they make responses larger.boolean
Include the reps (internal participants) in each call’s participants list.
boolean
Include Zoom-specific metadata (meeting IDs, etc).
boolean
Include import metadata (when the call was imported from another source).
boolean
Include linked CRM records (deals, accounts).
boolean
Include AI-extracted insights (intelligence item values).
transcript_search is used, results also include the matched transcript snippets.
Example prompt: “Find all calls discussing pricing in the last 30 days from the Enterprise team.”
get_call_details
Scope:
mcp:read.ask_attention instead — it’s an order of magnitude more efficient than calling get_call_details in a loop.
string
required
The call ID, returned by
search_calls.boolean
When
true, returns a structured transcript with speaker names and timestamps. When false (default), returns the simple text transcript.