Setting the file. One moment.
Subchapter 158.8
examples/transcript-retrieval.mdMarkdown3 KBView on GitHub
Use the Zoom MCP server when the goal is to search meeting content, retrieve meeting-linked assets, or fetch recording-oriented resources after a meeting.
Use this path when the user starts from content, topic, or time range.
meeting:read:searchmeeting:read:assetssearch_meetings
q: "Q4 budget discussion"
from: "2026-03-01"
to: "2026-03-06"
page_size: 20get_meeting_assets
meetingId: "MEETING_ID_OR_UUID"Expect the result to contain a meeting-linked asset bundle. In practice, this can include:
Do not hardcode exact field names without checking a current live response.
Use this path when the user needs transcript-capable resources, recording playback resources, or recording lookup by user/date range.
cloud_recording:read:list_user_recordingscloud_recording:read:contentrecordings_list
userId: "me"
from: "2026-03-01"
to: "2026-03-06"
page_size: 50get_recording_resource
meetingId: "MEETING_UUID_OR_RECORDING_ID"Use this when the user needs recording-oriented data such as:
| Need | Preferred path |
|---|---|
| Search by topic or what was discussed | search_meetings → get_meeting_assets |
| Inspect all meeting-linked assets | get_meeting_assets |
| List recordings by user/date | recordings_list |
| Fetch recording-oriented resources for a specific meeting | get_recording_resource |
If a returned recording resource includes a direct URL, fetch it with the same bearer token. The URL is not public by default.
search_meetings fails with missing scope:
meeting:read:searchget_meeting_assets fails with missing scope:
meeting:read:assetsrecordings_list fails with missing scope:
cloud_recording:read:list_user_recordingsget_recording_resource fails with missing scope:
cloud_recording:read:contentSearch results are sparse or low quality:
recordings_list if the user is really asking for post-meeting recording content