Skip to main content
Glama

google_calendar_delete_event

Remove an event from Google Calendar by specifying its event ID. Optionally, define the calendar ID or use the primary calendar by default.

Instructions

Delete an event from Google Calendar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdNoOptional: ID of calendar to use (defaults to primary if not specified)
eventIdYesID of the event to delete

Implementation Reference

  • The handler function that executes the tool: validates input using isDeleteEventArgs, extracts eventId and calendarId, calls deleteEvent on GoogleCalendar instance, and returns success response.
    export async function handleCalendarDeleteEvent(
      args: any,
      googleCalendarInstance: GoogleCalendar
    ) {
      if (!isDeleteEventArgs(args)) {
        throw new Error("Invalid arguments for google_calendar_delete_event");
      }
    
      const { eventId, calendarId } = args;
      const result = await googleCalendarInstance.deleteEvent(eventId, calendarId);
      return {
        content: [{ type: "text", text: result }],
        isError: false,
      };
    }
  • Tool schema definition: name, description, and inputSchema for google_calendar_delete_event.
    export const DELETE_EVENT_TOOL: Tool = {
      name: "google_calendar_delete_event",
      description: "Delete an event from Google Calendar",
      inputSchema: {
        type: "object",
        properties: {
          eventId: {
            type: "string",
            description: "ID of the event to delete",
          },
          calendarId: {
            type: "string",
            description:
              "Optional: ID of calendar to use (defaults to primary if not specified)",
          },
        },
        required: ["eventId"],
      },
    };
  • Registration in the server request handler switch statement: routes CallToolRequest for this tool to the handler.
    case "google_calendar_delete_event":
      return await calendarHandlers.handleCalendarDeleteEvent(
        args,
        googleCalendarInstance
      );
  • Helper validation function (type guard) used in the handler to validate arguments match the schema.
    export function isDeleteEventArgs(args: any): args is {
      eventId: string;
      calendarId?: string;
    } {
      return (
        args &&
        typeof args.eventId === "string" &&
        (args.calendarId === undefined || typeof args.calendarId === "string")
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Delete') but lacks critical details: it doesn't specify if deletion is permanent or reversible, what permissions are required, whether it affects recurring events, or what happens on success/failure. For a destructive operation with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by directly conveying the tool's purpose.

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?

Given the complexity of a destructive operation, lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permanence, permissions, or error handling, which are crucial for safe tool invocation. The high schema coverage helps with parameters, but overall context is inadequate for a mutation tool.

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%, with clear documentation for both parameters (calendarId and eventId). The description adds no parameter-specific information beyond what the schema provides, such as format examples or contextual usage. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

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 verb ('Delete') and resource ('an event from Google Calendar'), making the purpose unambiguous. It distinguishes from siblings like 'google_calendar_update_event' by specifying deletion rather than modification, though it doesn't explicitly contrast with other deletion tools like 'google_calendar_delete_event' (which doesn't exist in the list) or deletion tools in other services.

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. It doesn't mention prerequisites (e.g., needing an event ID from a previous operation), when not to use it (e.g., for soft deletion), or direct alternatives like 'google_calendar_update_event' to cancel instead of delete. Usage is implied only by the tool name and action.

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/vakharwalad23/google-mcp'

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