Skip to main content
Glama
JavaProgrammerLB

Zoom MCP Server

delete_a_meeting

Delete a Zoom meeting by providing its meeting ID. Removes the scheduled meeting permanently.

Instructions

Delete a meeting with a given ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the meeting to delete.

Implementation Reference

  • The actual handler function for 'delete_a_meeting'. It calls zoomRequest with a DELETE method to the Zoom API endpoint for the given meeting ID.
    export async function deleteMeeting(options: DeleteMeetingOptions) {
      const response = await zoomRequest(
        `https://api.zoom.us/v2/meetings/${options.id}`,
        {
          method: "DELETE",
        },
      );
      return response;
    }
  • The input schema (DeleteMeetingOptionsSchema) for 'delete_a_meeting'. Requires a numeric 'id' field for the meeting to delete.
    export const DeleteMeetingOptionsSchema = z.object({
      id: z.number().describe("The ID of the meeting to delete."),
    });
  • index.ts:137-140 (registration)
    Tool registration in ListToolsRequestSchema - declares the 'delete_a_meeting' tool with description and input schema.
      name: "delete_a_meeting",
      description: "Delete a meeting with a given ID",
      inputSchema: zodToJsonSchema(DeleteMeetingOptionsSchema),
    },
  • index.ts:172-178 (registration)
    Tool call handler case in CallToolRequestSchema - parses arguments with DeleteMeetingOptionsSchema and calls deleteMeeting().
    case "delete_a_meeting": {
      const args = DeleteMeetingOptionsSchema.parse(request.params.arguments);
      const result = await deleteMeeting(args);
      return {
        content: [{ type: "text", text: result }],
      };
    }
  • The zoomRequest helper utility used by deleteMeeting to make the actual HTTP DELETE call to the Zoom API.
    export async function zoomRequest(
      url: string,
      options: RequestOptions = {},
    ): Promise<unknown> {
      const token = (await getAccessToken()).access_token;
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        "User-Agent": USER_AGENT,
        Authorization: `Bearer ${token}`,
        ...options.headers,
      };
    
      const response = await fetch(url, {
        method: options.method || "GET",
        headers,
        body: options.body ? JSON.stringify(options.body) : undefined,
      });
    
      const responseBody = await parseResponseBody(response);
    
      if (!response.ok) {
        throw createZoomError(response.status, responseBody);
      }
    
      return responseBody;
    }
Behavior2/5

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

No annotations provided, and the description only states deletion by ID. Does not disclose irreversibility, side effects, or required permissions.

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

Conciseness5/5

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

Single sentence conveying all essential information with no wasted words.

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

Completeness3/5

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

For a simple deletion tool with one parameter and no output schema, the description provides adequate information. However, could mention that deletion is irreversible.

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

Parameters3/5

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

Schema coverage is 100%, and the id parameter is fully described. The description adds no additional meaning beyond the schema, resulting in baseline score.

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

Purpose5/5

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

The description clearly states the verb 'Delete' and the resource 'meeting' with a required ID. It effectively distinguishes from sibling tools like create_meeting, get_a_meeting_details, and list_meetings.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Lacks context about prerequisites or scenarios where deletion is appropriate.

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

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/JavaProgrammerLB/zoom-mcp-server'

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