Skip to main content
Glama
ricleedo

Google Services MCP Server

by ricleedo

calendar-delete-event

Remove calendar events from Google Calendar by specifying the event ID. This tool helps manage your schedule by deleting unwanted or outdated appointments.

Instructions

Delete a calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID
calendarIdNoCalendar ID - Available options: 'primary' (Primary Calendar)primary

Implementation Reference

  • src/index.ts:251-258 (registration)
    Registration of the 'calendar-delete-event' tool, linking to deleteEvent handler and deleteEventSchema.
    server.tool(
      "calendar-delete-event",
      "Delete a calendar event",
      deleteEventSchema().shape,
      async (params) => {
        return await deleteEvent(params);
      }
    );
  • Zod schema defining input parameters for deleting a calendar event: eventId and optional calendarId.
    export const deleteEventSchema = () =>
      z.object({
        eventId: z.string().describe("Event ID"),
        calendarId: z
          .string()
          .default("primary")
          .describe(getCalendarDescription()),
      });
  • Implementation of the deleteEvent handler: authenticates with Google Calendar API, deletes the specified event, and returns success or error message.
    // Delete event function
    export async function deleteEvent(
      params: z.infer<ReturnType<typeof deleteEventSchema>>
    ) {
      try {
        const auth = createCalendarAuth();
        const calendar = google.calendar({ version: "v3", auth });
    
        await calendar.events.delete({
          calendarId: params.calendarId,
          eventId: params.eventId,
          sendUpdates: "all",
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `# Event Deleted Successfully ✅\n\nEvent \`${params.eventId}\` has been deleted from your calendar.`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error deleting event: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't mention whether this is permanent, reversible, requires specific permissions, or what happens on success/failure. This is inadequate for a destructive operation with zero annotation coverage.

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 appropriately sized for a simple operation and gets straight to the point without unnecessary elaboration.

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 explain what happens after deletion, whether confirmation is needed, error conditions, or behavioral aspects. The description should provide more context given the tool's complexity and lack of structured metadata.

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?

The schema description coverage is 100%, so both parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema (eventId and calendarId with default). 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 ('a calendar event'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'calendar-update-event' or 'calendar-get-event' beyond the obvious action difference.

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. There's no mention of prerequisites (like needing an existing event), when not to use it, or how it differs from other calendar operations beyond the basic 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

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/ricleedo/Google-Service-MCP'

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