Setting the file. One moment.
Subchapter 158.6
examples/meeting-lifecycle.mdMarkdown1 KBView on GitHub
The current Zoom MCP surface does not expose deterministic meeting create, update, list, or delete tools.
If the user needs meeting lifecycle management, route to the REST API skill:
Use Zoom MCP for:
Use the REST API for:
Use MCP first when the user starts with meeting content or recap intent, then hand off to REST only if the next action becomes a deterministic resource-management step.
Example:
1. search_meetings
q: "client onboarding"
from: "2026-03-01"
to: "2026-03-06"
2. get_meeting_assets
meetingId: "MEETING_ID_OR_UUID"
3. If the user then wants to reschedule or delete the meeting,
route to zoom-rest-api and perform the CRUD operation there.