Zoom Revenue Accelerator

## Tool Description Batch AI analysis endpoint for Zoom Revenue Accelerator conversations. Accepts up to 20 conversation IDs per request and returns structured AI-generated analysis such as summary, sentiment, next steps, good questions, topics, indicators, deal memo, and speaker metrics. ## When to Use Use this tool when you need to retrieve AI-generated insights for one or more sales conversations, such as generating meeting summaries, evaluating sentiment, extracting action items, reviewing deal health signals, or analyzing speaker metrics. For raw spoken content, use `get_conversation_transcript` instead. ## Must Do - Always provide at least one conversation ID in `conversation_ids` - Explicitly provide `analysis_types` when you only need specific analysis sections, to reduce response payload and improve efficiency - If `analysis_types` is omitted or empty, all available analysis types are returned - Limit requests to a maximum of 20 conversation IDs; IDs beyond the 20th are silently ignored ## Error Handling - If a conversation is inaccessible or has no analysis data, its entry is still returned but with an empty analysis object — this is not an error - Absent fields in the analysis object indicate either the type was not requested or no data exists for that section - `summary` may be truncated to 5 KB (UTF-8); no trailing marker is added - `indicators` list is deduplicated by indicator ID ## Call Chain - UPSTREAM: Call search_conversations first to obtain conversation_ids - DOWNSTREAM: No further tools needed

## Tool Description Retrieves all comments posted on a specific Zoom Revenue Accelerator conversation. Returns all comments in a single response (no pagination), including each comment's author (user_id, display name, email) and text content. ## When to Use Use this tool when the user wants to review discussion threads, coaching feedback, or annotations added to a conversation recording. ## Must Do - Always provide `conversation_id` (obtained from search_conversations) ## Error Handling - Returns an empty data_items list when the conversation has no comments - `text` is truncated at 500 characters ## Call Chain - UPSTREAM: Call search_conversations first to obtain the conversation_id - DOWNSTREAM: No further tools needed

## Tool Description Retrieves the full transcript of a specific Zoom Revenue Accelerator conversation. Returns a compact token-optimized transcript string where each line is prefixed with a numeric speaker ID, plus a speaker_defs list that maps each ID to the speaker's display name and role. Optionally filters to only segments containing a keyword. ## When to Use Use this tool when you need access to the raw spoken content of a conversation — for example, to find specific quotes, verify what was said, or analyze dialogue in detail. For AI-extracted insights such as summary, action items, and sentiment, use `get_conversation_analysis` instead. ## Must Do - Always provide `conversation_id` (obtained from search_conversations) - Use `keyword` to narrow transcript output when looking for specific topics — this reduces token consumption significantly ## Error Handling - If the conversation has no transcript or no segments match the keyword, `transcript` returns an empty string "" - Speaker IDs in the transcript string are numeric (e.g., "1:", "2:") — use speaker_defs to resolve them to display names ## Call Chain - UPSTREAM: Call search_conversations first to obtain the conversation_id - DOWNSTREAM: No further tools needed

## Tool Description Retrieves customer account records from Zoom Revenue Accelerator. Returns company profile details (industry, domain, website, employee count, annual revenue), CRM integration identifiers, ownership, and deal/contact counts. Supports lookup by account IDs or keyword search. ## When to Use Use this tool when the user refers to a company by name and you need the internal account_id — for example, before filtering conversations, deals, or contacts for a specific company. Also use it to retrieve general account profile information. ## Must Do - Use `keyword` to search by company name when you don't already have the account_id - Confirm the correct account with the user if the keyword returns multiple results with similar names ## Error Handling - Returns an empty `accounts` array when no accounts match the query - If no exact company match is found, try a shorter or less specific keyword ## Call Chain - UPSTREAM: No dependencies - DOWNSTREAM: account_id → get_customer_contacts (customer_account_id), search_deals (customer_account_id), search_conversations (customer_account_id)

## Tool Description Retrieves customer contact records from Zoom Revenue Accelerator. Returns contact profile (name, email, phone, job title), company affiliation, last engagement date, deal count, and optionally recent deals, recent meetings, and custom CRM fields. ## When to Use Use this tool when you need to look up external customer contacts — for example, to find a contact's ID before filtering conversations by that contact, or to review their recent deal and meeting history. ## Must Do - Use `customer_account_id` to scope the search when looking for contacts at a specific company (obtain it from get_customer_accounts first) - Set `include_recent_deals=true` only when deal history is specifically needed — it increases response payload - Set `include_recent_meetings=true` only when meeting history is specifically needed ## Error Handling - Returns an empty `contacts` array when no contacts match the filter - `recent_deal` is absent when the contact has no associated deals, or when `include_recent_deals` is `false` - `recent_meetings` is absent or empty when the contact has no associated meetings, or when `include_recent_meetings` is `false` - `custom_data` is absent or empty when no custom CRM data exists, or when `include_custom_data` is `false` ## Call Chain - UPSTREAM: get_customer_accounts → customer_account_id (scope to a company) - DOWNSTREAM: contact_id → search_conversations (customer_contact_ids)

## Tool Description Returns a paginated list of activities (meetings, calls, emails) logged against a specific CRM deal. Supports filtering by activity type, date range, and optional content inclusion. Also returns participants and the deal stage at the time of each activity. ## When to Use Use this tool when the user wants to review the interaction history for a specific deal — for example, how many calls have been made, what was discussed in recent meetings, or who participated in deal activities. ## Must Do - Always provide `deal_id` (obtained from search_deals) - Set `include_content=true` only when activity content (call summary / meeting description) is specifically needed — it increases response payload - For best performance, keep date range within one month ## Error Handling - Returns an empty `data_items` array when no activities match the filters - `next_page_token` is empty when there are no more pages ## Call Chain - UPSTREAM: Call search_deals first to obtain the deal_id - DOWNSTREAM: No further tools needed

## Tool Description Performs AI-driven analysis on a specific CRM deal. Returns a STORY (narrative summary of the deal's progression and current status) and/or a PLAYBOOK evaluation (per-element compliance notes against configured sales methodologies such as MEDDIC). Both types can be requested in a single call. ## When to Use Use this tool when you need to understand the overall health, momentum, and risks of a specific deal, or to evaluate the deal against a sales playbook methodology. Call `get_deal_detail_v2` first if you also need structured deal data such as stage, amount, or contacts. ## Must Do - Always provide `deal_id` (obtained from search_deals) - Set `analysis_type` to STORY, PLAYBOOK, or ALL (default when omitted) ## Error Handling - If the deal has no analysis data for the requested type, the corresponding field (deal_story or playbook_items) is absent from the response — this is expected for newly created deals or deals without sufficient activity - `playbook_items` is absent when no playbook is configured for the deal ## Call Chain - UPSTREAM: Call search_deals first to obtain the deal_id - DOWNSTREAM: No further tools needed

## Tool Description Batch-fetches full deal details for up to 20 deal IDs. Returns comprehensive deal data including pipeline stage, value, owner, customer account, activity count, contact count, trend indicators, deal team members, key contacts, and optionally custom CRM fields. ## When to Use Use this tool after search_deals when you need complete deal information beyond the summary fields — for example, to review team composition, key contacts, or custom CRM fields for deal preparation or board review. ## Must Do - Always provide `deal_ids` (obtained from search_deals); maximum 20 per request - Set `include_custom_fields=true` only when CRM custom fields are specifically needed — it increases response payload ## Error Handling - Returns only the deals the caller has access to; inaccessible deal IDs are silently excluded - `total` in the response reflects the number of deals actually returned, not the number of IDs requested ## Call Chain - UPSTREAM: Call search_deals first to obtain the deal_ids - DOWNSTREAM: customer_account_id → get_customer_accounts; deal_id → get_deal_analysis, get_deal_activities_v2

## Tool Description Retrieves the list of CRM deal pipeline stages configured for this account. Returns each stage's display name, sort order, and flags indicating whether it is a closed stage and whether it represents a won deal. ## When to Use Use this tool before filtering deals by stage (search_deals → deal_stages), or when the user asks about available pipeline stages. Call it once at the start of a deal workflow to obtain valid stage names. ## Must Do - Use the exact stage names from the response when passing to search_deals ## Error Handling - Returns an empty stages list when no stages are configured for the account ## Call Chain - UPSTREAM: No dependencies - DOWNSTREAM: stage names → search_deals (deal_stages)

## Tool Description Retrieves team information in Zoom Revenue Accelerator. When called without `team_ids`, it returns teams managed by the current user together with their managers. When called with `team_ids`, it returns detailed recursive member lists for the specified teams. ## When to Use Use this tool ONLY when: - The user asks about team structure, team members, or team managers - `search_conversations` or `search_deals` needs `team_ids` for `scope=SPECIFIC` — i.e., the user names a specific team Do NOT use this tool when `scope=MY_MANAGED` — that scope does not require team_ids ## Must Do - Start with overview mode (omit `team_ids`) to discover teams managed by the current user - Use detail mode (provide `team_ids`) only when you need the full member list for one or more specific teams - `members` is capped at 200 entries per team in detail mode ## Error Handling - Returns an empty `items` array when the current user manages no teams - `members` is only present in detail mode ## Call Chain - UPSTREAM: No dependencies - DOWNSTREAM (only when scope=SPECIFIC): `team_id` -> `search_conversations` (`team_ids`), `search_deals` (`team_ids`)