Skip to main content
Glama

get_meeting_recordings

Retrieve Zoom meeting recordings by providing the meeting ID. This tool integrates with the Zoom API MCP Server to securely access and manage recordings with structured validation and OAuth 2.0 authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYesThe meeting ID

Implementation Reference

  • Handler function that retrieves recordings for a specific meeting using the Zoom API.
    handler: async ({ meeting_id }) => {
      try {
        const response = await zoomApi.get(`/meetings/${meeting_id}/recordings`);
        return handleApiResponse(response);
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod input schema defining the required meeting_id parameter.
    schema: {
      meeting_id: z.string().describe("The meeting ID")
    },
  • Tool object definition for get_meeting_recordings, registered into the recordingsTools array.
    {
      name: "get_meeting_recordings",
      description: "Get recordings for a specific meeting",
      schema: {
        meeting_id: z.string().describe("The meeting ID")
      },
      handler: async ({ meeting_id }) => {
        try {
          const response = await zoomApi.get(`/meetings/${meeting_id}/recordings`);
          return handleApiResponse(response);
        } catch (error) {
          return handleApiError(error);
        }
      }
    },
  • src/server.js:53-53 (registration)
    Top-level registration of the recordingsTools array to the MCP server, including the get_meeting_recordings tool.
    registerTools(recordingsTools);
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattcoatsworth/zoom-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server