Zoom

# Ask **READ-ONLY** Returns one synthesized answer with citations from the user's accessible Zoom workspace and connected files. Datasource scopes are `zoom_meeting`, `zoom_chat_message`, `zoom_chat_session`, `zoom_canvas`, `zoom_my_notes`, `zoom_phone_call`, `zoom_phone_sms`, `zoom_phone_voicemail` and `third_party_file`. ## Tool selection Ask suits summaries, explanations, comparisons, status, decisions, owners, risks, themes, and action items. Search suits get, find, list, browse, and open requests returning matching records. ## Ask planning 1. **Form the request.** Supply the complete natural-language task through `query`. Ask combines semantic retrieval, content retrieval, and reasoning. Relative or local time expressions are resolved internally using the user's time zone from their Zoom profile, so callers do not supply UTC boundaries or separately request the time zone. 2. **Route by requested object.** Select datasources for the artifacts the user wants returned; a person, meeting, date, or platform that identifies an artifact is a constraint, not another requested family. Combine datasources only when the user independently requests multiple families or the requested artifact can belong to multiple families and the wording does not disambiguate it. - `zoom_my_notes` covers authorized notes and attendee-side transcripts from Zoom, third-party, and in-person meetings, including notes created by the user, shared with them, or moved outside the My Notes folder; “My Notes” is a product collection rather than a creator filter. - `zoom_meeting` covers host-owned meeting records, summaries, cloud recordings, and their recording transcripts. - When a transcript request does not specify whether it means an attendee-side/My Notes transcript or a recording transcript, include both `zoom_my_notes` and `zoom_meeting`; meeting context alone does not resolve that ambiguity. - `zoom_chat_session` covers chat groups and channels. - `zoom_chat_message` covers message content. - `zoom_canvas` covers Zoom Docs. - `zoom_phone_call` covers Zoom Phone call records. - `zoom_phone_sms` covers Zoom Phone SMS messages. - `zoom_phone_voicemail` covers Zoom Phone voicemail records. - `third_party_file` covers connected files and uses `source` for the provider; if source values are unknown, request `third_party_file` from Search Describe Capabilities before Ask. 3. **Set context.** Restrict `datasources` when the evidence scope is known. If it is broad or unclear, omit `datasources` to search all supported Ask sources. Use `context_resources` for known resources and `chat_history` for prior turns. Datasource selection changes retrieval scope, not the synthesized response format. Ask does not accept metadata filters or return pageable raw records. Search provides exact counts, pagination, and field-level filtering. An Ask answer does not change the meaning of an empty exact Search result. ## Parameters - **`query`** (string, required) — Complete natural-language question or instruction. - **`chat_history`** (array, optional) — Prior `{role, content}` turns in chronological order. Ask is stateless when history is omitted. - **`context_resources`** (array, optional) — Known resources to include as context, identified by `datasource` and datasource-specific identifiers. A third-party file uses `source` and `file_id`. - **`datasources`** (array, optional) — Strictly limits retrieval to the listed datasource scopes. A third-party scope uses `source`; omission searches all supported Ask sources. ## Response Returns `request_id`, an assistant `message`, and `citations`. Citations may contain a title, excerpt, URL, entity type, datasource, and datasource-specific metadata. `message.content` is the completed synthesis rather than raw evidence and can be presented directly with its citations. Formatting should preserve its meaning and attribution without introducing additional claims.

Adds collaborators (Zoom users, Team Chat channels, or email addresses) to a Zoom Canvas (formerly Zoom Docs) file, granting them a specified access role. Only `doc` or `data table` file types are supported. ## When to Use Use this tool when a user wants to share a Canvas file with one or more people or channels by assigning them viewer, commenter, editor, or co-owner permissions. ## Must Do - Each collaborator entry **must** include exactly one identifier: `user_id`, `channel_id`, or `email` - Each collaborator entry **must** include a `role` (`viewer`, `commenter`, `editor`, or `co-owner`) - Provide between **1 and 50** collaborators per request - The target file must be of type `doc` or `data table` ## Must NOT Do - Do **not** include more than one identifier field (`user_id`, `channel_id`, `email`) per collaborator entry - Do **not** use this tool on unsupported file types (e.g., spreadsheets, presentations)

Retrieves the list of collaborators for a specified Zoom Canvas (formerly Zoom Docs) file (supports `doc` and `data table` file types only). ## When to Use Use this tool when you need to view who has access to a Zoom Canvas file, including their roles and collaborator types (user, channel, or email). ## Must Do - Provide a valid `fileId` from Zoom Canvas - Only use with `doc` or `data table` file types ## Output Returns up to 50 collaborators, each containing: - `collaborator_id`: Use this ID when removing or modifying a collaborator - `collaborator_type`: One of `user`, `channel`, or `email` - `role`: One of `viewer`, `commenter`, `editor`, or `co-owner` - `collaborator_name`: Display name - Conditional identity field: `user_id` (if type=user), `channel_id` (if type=channel), or `email` (if type=email)

Modifies the role of an existing collaborator on a Zoom Canvas (formerly Zoom Docs) file. Only `doc` or `data table` file types are supported. ## When to Use Use this tool when you need to change a collaborator's permission level (e.g., upgrading a viewer to an editor, or demoting a co-owner to a commenter) on a specific Zoom Canvas file. ## Must Do - Provide the file ID, collaborator ID, and the new role - Ensure the target file is of type `doc` or `data table` - Use one of the valid role values: `viewer`, `commenter`, `editor`, or `co-owner`

Removes a specified collaborator from a file in Zoom Canvas (formerly Zoom Docs). Only `doc` or `data table` file types are supported. ## When to Use Use this tool when a user wants to revoke a collaborator's access to a specific Zoom Canvas file (doc or data table). ## Prerequisites - You must have the **file ID** of the target document in Zoom Canvas. - You must have the **collaborator item ID** to identify which collaborator to remove (obtainable via a "list collaborators" operation). ## Must Do - Ensure the target file is of type `doc` or `data table` before attempting removal. ## Must NOT Do - Do not use this tool on unsupported file types (e.g., files other than `doc` or `data table`).

## Tool Description ⚠️ DEPRECATED: This tool has been replaced by `hub_create_file_from_content`. DO NOT use this tool. Use `hub_create_file_from_content` instead for creating files with Markdown content. ## When to Use DO NOT use this tool. It is deprecated and no longer maintained. ## Must NOT Do - DO NOT call this tool for any new requests. - DO NOT use this tool when the user wants to create a file with content. ## Migration Use `hub_create_file_from_content` as the direct replacement for all file creation with Markdown content tasks.

## Tool Description [DEPRECATED] This tool is deprecated. Please use `hub_get_file_content` instead for all future file content retrieval tasks. Retrieves the full Markdown content and file name of an existing Zoom Docs (Zoom Canvas) document using its file ID. ## When to Use ⚠️ **This tool is deprecated. Use `hub_get_file_content` as the replacement.** Only use this tool as a fallback if `hub_get_file_content` is unavailable. Use this tool when you need to read the full content of a Zoom Docs file by its file ID, in either structured XML format (for block-level editing) or plain Markdown format (for reading only). ## Must Do - Always prefer `hub_get_file_content` over this tool for all new tasks. - Use `xml` format when block-level editing is planned, as it is the ONLY format that exposes block IDs required by block-level edit tools (docs_file_insert_blocks, docs_file_update_block, docs_file_delete_block, docs_file_replace_range_of_blocks). - Use `markdown` format only when plain text reading is sufficient and no block-level editing is needed. ## Must NOT Do - Do NOT use `markdown` format when block-level editing is planned, as it does not expose block IDs.

# Get Meeting Assets V4.0 **READ-ONLY** Retrieve all available assets for a specific Zoom meeting, including AI summaries, My Notes, cloud recordings, whiteboards, Zoom Docs, agenda documents, and participants. ## When to use this tool - User wants to retrieve assets for a completed meeting - User needs access to meeting summaries,My Notes, recordings, whiteboards, Zoom Docs, agenda, or participant information - User provides a meeting identifier (numeric meeting ID or UUID) **Required condition:** User must provide a meeting ID (numeric or UUID format) to use this tool. ## Parameters ### `meetingId` (String, Required) The meeting identifier. Accepts either: 1. **UUID** (preferred) — e.g., `"38DCDB7C-74B1-442F-BE85-390DF0BB96CC"`. Targets a specific meeting instance. 2. **Numeric meeting ID** — e.g., `"123456789"`. Returns assets for the latest meeting instance when multiple instances exist. Always prefer UUID when available; numeric ID cannot target specific past instances of recurring meetings. ## Response Returns a JSON object containing the following asset fields (each may be `null` if unavailable): - `meeting_summary` — AI-generated summary with quick recap, full text, and next steps - `my_notes` — User notes and participant transcripts recorded during the meeting - `recording` — Cloud recording with play URL, duration, and processing status - `whiteboards` — Whiteboards shared or created during the meeting - `docs` — Zoom Docs linked to the meeting - `agenda_doc` — Agenda document associated with the meeting - `participants` — Meeting participant list ## Access Control Only the meeting host or participants explicitly granted access by the host can retrieve meeting assets. Unauthorized requests return a permission error. ## Error Handling | Error | Meaning | |-------|---------| | 403 / Permission denied | User lacks access to this meeting's assets. | | 404 / Not found | Invalid, expired, or unrecognized meeting ID/UUID. | ## Usage Notes - Cloud recordings may show `processing: true` while still being generated after a meeting ends. - AI summaries require AI Companion to have been enabled and sufficient meeting duration. - It is normal for a meeting to have some asset types but not others (e.g., recording but no summary). - Timestamps are in UTC (ISO 8601). Convert to the user's local timezone for display.

**Description:** Retrieves detailed content and metadata for a specific Zoom recording, including transcript text, topic summaries, next steps/action items, and playback URLs. Use this tool when the user explicitly mentions "recording" or requests content-level details (e.g., "What did they say about X?", "Play the recording", "Find the part where they discussed pricing"). For general meeting discovery or meeting-level metadata without recording context, prefer the Assets tool. **Parameters:** - **types** *(string, optional)*: Comma-separated list of resource types to retrieve. Valid values: `transcript`, `summary`, `nextStep`, `playUrl`. If omitted or empty, all available types are returned. Include `transcript` when answering content questions; include both `transcript` and `playUrl` when the user wants to jump to a specific moment. - **raw_passcode** *(string, optional)*: Plaintext passcode for the recording (up to 10 characters; letters, digits, or special characters). - **encode_passcode** *(string, optional)*: Encrypted passcode from the `pwd=` parameter of a Zoom share link. - **clip_num** *(integer, optional)*: 1-based index of the clip to retrieve for multi-clip recordings. Returns null if the index exceeds available clips. - **play_time** *(integer, optional)*: Playback start time in seconds within the selected clip (e.g., `20` = start 20 seconds in). Use transcript timestamps to determine the appropriate value when the user asks to jump to a specific topic. **Return Schema Overview:** ```json { "transcripts": [{ "timeline": [{ "text", "ts", "end_ts", "display_name" }], "recording_id", "meeting_id", "recording_start", "recording_end" }], "summaries": [{ "overall_summary", "items": [{ "label", "summary" }], "recording_start", "total_items" }], "next_steps": [{ "items": [{ "text" }], "recording_start", "total_items" }], "play_urls": [{ "urls": ["string"], "recording_start", "play_time" }] } ``` Fields are omitted if no data exists for that type. **Usage Notes:** - Recording duration = `recording_end − recording_start`. - To navigate to a topic: first retrieve `transcript` to find the relevant timestamp, then use that value as `play_time` alongside `playUrl`. - When user intent is ambiguous (content + playback), omit `types` to fetch all resources. - Tool selection rule: **recording keyword or playback action present → this tool; general meeting queries → Assets tool first.**

## Tool Description Creates a new Zoom Hub file (doc, paper_doc, or spreadsheet) from plain-text content and returns the file ID and deep link. ## Prerequisites - `parent_id` is OPTIONAL. - DO NOT specify `parent_id` unless the user explicitly tells you where to save the file. - If the user does not mention a folder or location, omit `parent_id` entirely — do not default it to "root" or empty string. - Only provide `parent_id` when the user explicitly provides a valid folder ID or path. ✅ Correct: omit parent_id when user says "Generate a sample sales spreadsheet for me." ❌ Wrong: parent_id = "root" ← do not assume this as default ## When to Use Use this tool when the user wants to create a new document, paper document, or spreadsheet in Zoom Hub with specific text content (Markdown for docs/paper_docs, CSV for spreadsheets). ## Prerequisites - For `parent_id`: use empty string or `"root"` to place in the caller's My Files folder, or provide a valid folder ID owned by or shared with the caller ## Must Do - Set `file_type` to one of: `doc`, `paper_doc`, or `spreadsheet` - Use **Markdown format** for `doc` or `paper_doc` content - Use **CSV format** for `spreadsheet` content - Keep `content` size ≤ 100 KB ## Must NOT Do - Do **not** use `file_type=presentation` — slide-deck import is not supported ## Error Handling - `400 REASON_PARAMS_INVALID`: Invalid parameters (e.g., attempting to create a presentation or exceeding content size limit)