Skip to main content
Calls are the foundation of every other read flow. 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.
When the user mentions a company name, always run two searches in parallel: one filtered by title, and one filtered by CRM account name (crm_field_entity_code="account", crm_field_field_name="Name", crm_field_values=["Acme"]). Merge and deduplicate the IDs. This catches calls whose title doesn’t include the company name but whose linked CRM account does.

​
Tools

​
search_calls

Scope: mcp:read.
Search recorded calls by date, rep, team, keyword, opportunity, CRM field, or transcript content. Results are scoped to calls your user can see.

​
Pagination

​
page
integer
Page number (starts from 1).
​
size
integer
Number of calls per page. Maximum: 50.

​
Date range

​
from_date
string
Show calls after this date. Format: 2024-01-01T00:00:00Z.
​
to_date
string
Show calls before this date. Format: 2024-12-31T23:59:59Z.

​
Owner & team

​
rep_email
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.
​
rep_id
string
Filter by call owner user ID. Alternative to rep_email.
​
team_id
string
Filter by team ID. Results are already scoped to your accessible teams based on your role.

​
Keyword & participants

​
title
string
Search calls by title keyword.
​
participant_email
string
Filter by external participant email.
​
transcript_search
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

​
opportunity_id
string
Filter by CRM opportunity/deal ID. The preferred way to find calls linked to a specific opportunity.
​
crm_field_entity_code
string
CRM entity code (e.g. opportunity, account, contact). Required together with crm_field_field_name and crm_field_values.
​
crm_field_field_name
string
CRM field name to match (e.g. StageName, Name). Required together with crm_field_entity_code and crm_field_values.
​
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.
​
hide_internal
boolean
Exclude internal-only meetings.
​
hide_non_analyzed
boolean
Exclude calls that haven’t been analyzed.
​
hide_pending
boolean
Exclude calls that are still pending processing.
​
hide_failed
boolean
Exclude calls whose processing failed.
​
hide_transcript
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.
​
include_internal_participants
boolean
Include the reps (internal participants) in each call’s participants list.
​
include_zoom_metadata
boolean
Include Zoom-specific metadata (meeting IDs, etc).
​
include_import_metadata
boolean
Include import metadata (when the call was imported from another source).
​
with_crm_records
boolean
Include linked CRM records (deals, accounts).
​
with_intelligence_items
boolean
Include AI-extracted insights (intelligence item values).
Returns: A Markdown list of matching calls — title, date, rep, participants, score, and ID — with pagination context. When 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.
Get details for a single call: full transcript, scorecard results, AI-extracted insights, participants, and CRM linkage. Use this when the user asks to read or see the transcript. For analysis across multiple calls, use ask_attention instead — it’s an order of magnitude more efficient than calling get_call_details in a loop.
​
id
string
required
The call ID, returned by search_calls.
​
detailed_transcript
boolean
When true, returns a structured transcript with speaker names and timestamps. When false (default), returns the simple text transcript.
Returns: A Markdown document with the call’s title, date, participants, score, transcript, and AI-extracted insights. Example prompt: “Show me the full transcript of my call with Acme yesterday, with speaker names and timestamps.”