Skip to main content
Glama
rishipradeep-think41

Google Workspace MCP Server

delete_event

Remove a specific calendar event using its unique event ID to manage Google Calendar entries programmatically via the Google Workspace MCP Server.

Instructions

Delete a calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID to delete

Implementation Reference

  • src/index.ts:255-268 (registration)
    Registration of the 'delete_event' tool in the ListTools response, including name, description, and input schema.
    {
      name: "delete_event",
      description: "Delete a calendar event",
      inputSchema: {
        type: "object",
        properties: {
          eventId: {
            type: "string",
            description: "Event ID to delete",
          },
        },
        required: ["eventId"],
      },
    },
  • The handler function that executes the delete_event tool by deleting the specified calendar event using the Google Calendar API.
    private async handleDeleteEvent(args: any) {
      try {
        const { eventId } = args;
    
        await this.calendar.events.delete({
          calendarId: "primary",
          eventId,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Event deleted successfully. Event ID: ${eventId}`,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: "text",
              text: `Error deleting event: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema definition for the delete_event tool, specifying the required 'eventId' parameter.
    inputSchema: {
      type: "object",
      properties: {
        eventId: {
          type: "string",
          description: "Event ID to delete",
        },
      },
      required: ["eventId"],
    },
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 ('Delete') but lacks critical details: it doesn't specify if deletion is permanent or reversible, mention authentication requirements, warn about side effects, or describe error handling. 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 front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permanence or permissions, return values, or error cases. Given the complexity of deletion operations and lack of structured data, more context is needed for safe and effective use.

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 the single parameter 'eventId' documented as 'Event ID to delete'. The description adds no additional meaning beyond this, such as format examples or sourcing instructions. Baseline 3 is appropriate since the schema already fully describes the parameter.

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 'Delete a calendar event' clearly states the verb ('Delete') and resource ('calendar event'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update_event' or 'create_event' beyond the basic action, missing specific scope details that would distinguish it more clearly.

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 existing event ID), exclusions (e.g., not for modifying events), or refer to sibling tools like 'update_event' for non-destructive changes, leaving the agent without context for tool selection.

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/rishipradeep-think41/gsuite-mcp'

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