Skip to main content
Glama

delete_recording_file

Remove Zoom meeting recordings by specifying the meeting ID and recording ID. Choose to move the file to trash or delete it permanently using the specified action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoDelete action (trash: move to trash, delete: delete permanently)
meeting_idYesThe meeting ID
recording_idYesThe recording ID

Implementation Reference

  • The handler function that executes the logic for deleting a specific recording file using the Zoom API DELETE request to /meetings/{meeting_id}/recordings/{recording_id}.
    handler: async ({ meeting_id, recording_id, action }) => {
      try {
        const params = {};
        if (action) params.action = action;
        
        const response = await zoomApi.delete(`/meetings/${meeting_id}/recordings/${recording_id}`, { params });
        return {
          content: [{ 
            type: "text", 
            text: "Recording file deleted successfully"
          }]
        };
      } catch (error) {
        return handleApiError(error);
      }
    }
  • Zod schema for input validation of the delete_recording_file tool parameters: meeting_id, recording_id, and optional action.
    schema: {
      meeting_id: z.string().describe("The meeting ID"),
      recording_id: z.string().describe("The recording ID"),
      action: z.enum(["trash", "delete"]).optional().describe("Delete action (trash: move to trash, delete: delete permanently)")
    },
  • The tool definition object for delete_recording_file, including name, description, schema, and handler, which is part of the recordingsTools array exported and later registered in the MCP server.
    {
      name: "delete_recording_file",
      description: "Delete a specific recording file",
      schema: {
        meeting_id: z.string().describe("The meeting ID"),
        recording_id: z.string().describe("The recording ID"),
        action: z.enum(["trash", "delete"]).optional().describe("Delete action (trash: move to trash, delete: delete permanently)")
      },
      handler: async ({ meeting_id, recording_id, action }) => {
        try {
          const params = {};
          if (action) params.action = action;
          
          const response = await zoomApi.delete(`/meetings/${meeting_id}/recordings/${recording_id}`, { params });
          return {
            content: [{ 
              type: "text", 
              text: "Recording file deleted successfully"
            }]
          };
        } catch (error) {
          return handleApiError(error);
        }
      }
    }
  • src/server.js:53-53 (registration)
    The call to registerTools(recordingsTools) which registers all tools in the array, including delete_recording_file, by calling server.tool for each.
    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