Skip to main content
Glama

delete_meeting

Remove scheduled Zoom meetings by specifying the meeting ID, cancel recurring occurrences with the occurrence ID, and optionally notify registrants via email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idYesThe meeting ID
occurrence_idNoThe occurrence ID for a recurring meeting
schedule_for_reminderNoSend cancellation email to registrants

Implementation Reference

  • The handler function that executes the tool logic by making a DELETE request to the Zoom API endpoint `/meetings/${meeting_id}` with optional parameters for recurring occurrences and reminders. It returns a success message or handles errors using handleApiError.
    handler: async ({ meeting_id, occurrence_id, schedule_for_reminder }) => {
      try {
        const params = {};
        if (occurrence_id) params.occurrence_id = occurrence_id;
        if (schedule_for_reminder !== undefined) params.schedule_for_reminder = schedule_for_reminder;
        
        const response = await zoomApi.delete(`/meetings/${meeting_id}`, { params });
        return {
          content: [{ 
            type: "text", 
            text: "Meeting deleted successfully"
          }]
        };
      } catch (error) {
        return handleApiError(error);
      }
  • Zod schema for input validation: requires meeting_id, optionally accepts occurrence_id for recurring meetings and schedule_for_reminder boolean.
    schema: {
      meeting_id: z.string().describe("The meeting ID"),
      occurrence_id: z.string().optional().describe("The occurrence ID for a recurring meeting"),
      schedule_for_reminder: z.boolean().optional().describe("Send cancellation email to registrants")
    },
  • src/server.js:46-46 (registration)
    Registers the meetingsTools array (which includes the delete_meeting tool definition) by calling registerTools, which in turn calls server.tool() for each tool with its name, schema, handler, and description.
    registerTools(meetingsTools);
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