Skip to main content
Glama
peadams21

Google Calendar MCP Server

by peadams21

delete_event

Remove events from Google Calendar to manage schedules and keep calendars organized. Specify the calendar and event ID to delete specific appointments or meetings.

Instructions

Delete an event from Google Calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdNoCalendar ID (default: 'primary')primary
eventIdYesEvent ID to delete

Implementation Reference

  • The handler function that performs the actual deletion of the event using the Google Calendar API's events.delete method, with success/error response formatting.
    async function handleDeleteEvent(args: z.infer<typeof DeleteEventArgsSchema>) {
      try {
        await calendar.events.delete({
          calendarId: args.calendarId,
          eventId: args.eventId,
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: true,
                message: `Event "${args.eventId}" deleted successfully`,
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                success: false,
                error: error instanceof Error ? error.message : "Unknown error",
              }, null, 2),
            },
          ],
          isError: true,
        };
      }
    }
  • Zod schema for input validation of delete_event tool arguments: optional calendarId and required eventId.
    const DeleteEventArgsSchema = z.object({
      calendarId: z.string().optional().default("primary"),
      eventId: z.string(),
    });
  • src/index.ts:292-310 (registration)
    Tool registration in the tools array, including name, description, and JSON input schema for the MCP server's list_tools response.
    {
      name: "delete_event",
      description: "Delete an event from Google Calendar",
      inputSchema: {
        type: "object",
        properties: {
          calendarId: {
            type: "string",
            description: "Calendar ID (default: 'primary')",
            default: "primary",
          },
          eventId: {
            type: "string",
            description: "Event ID to delete",
          },
        },
        required: ["eventId"],
      },
    },
  • src/index.ts:559-562 (registration)
    Dispatch logic in the CallToolRequestSchema handler that validates arguments and invokes the delete_event handler.
    case "delete_event": {
      const validatedArgs = DeleteEventArgsSchema.parse(args);
      return await handleDeleteEvent(validatedArgs);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is destructive ('Delete'), but doesn't mention permissions required, whether deletion is reversible, rate limits, or what happens to associated data. This leaves significant gaps for a mutation tool.

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?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and efficient.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address behavioral aspects like permissions, reversibility, or error conditions, nor does it explain what happens upon success. Given the complexity and lack of structured data, more context is needed.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional parameter context beyond implying 'eventId' identifies what to delete. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Delete') and resource ('an event from Google Calendar'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'update_event' or 'create_event', but it's unambiguous about its specific function.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update_event' or 'create_event'. There's no mention of prerequisites (e.g., needing an existing event ID) or contextual cues for when deletion is appropriate versus modification.

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/peadams21/Google-Calendar-MCP-Server'

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