list_recordings
Fetch Zoom meeting recordings by user ID within a specified date range, retrieve paginated results, and manage data efficiently using the MCP Server's Zoom API integration.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Start date in 'yyyy-MM-dd' format | |
| next_page_token | No | Next page token | |
| page_size | No | Number of records returned | |
| to | No | End date in 'yyyy-MM-dd' format | |
| user_id | Yes | The user ID or email address |
Implementation Reference
- src/tools/recordings.js:15-28 (handler)The handler function that implements the core logic of the 'list_recordings' tool by calling the Zoom API to fetch recordings for a given user with optional pagination and date range parameters.handler: async ({ user_id, page_size, next_page_token, from, to }) => { try { const params = {}; if (page_size) params.page_size = page_size; if (next_page_token) params.next_page_token = next_page_token; if (from) params.from = from; if (to) params.to = to; const response = await zoomApi.get(`/users/${user_id}/recordings`, { params }); return handleApiResponse(response); } catch (error) { return handleApiError(error); } }
- src/tools/recordings.js:8-14 (schema)The Zod schema defining the input parameters and their validation rules for the 'list_recordings' tool.schema: { user_id: z.string().describe("The user ID or email address"), page_size: z.number().min(1).max(300).optional().describe("Number of records returned"), next_page_token: z.string().optional().describe("Next page token"), from: z.string().optional().describe("Start date in 'yyyy-MM-dd' format"), to: z.string().optional().describe("End date in 'yyyy-MM-dd' format") },
- src/server.js:53-53 (registration)The line where the recordingsTools array (containing the 'list_recordings' tool) is registered with the MCP server.registerTools(recordingsTools);