Google Calendar and Meet MCP Server

calendar_v3_delete_event

Remove scheduled events from Google Calendar using the Calendar API v3 by specifying event and calendar IDs.

Instructions

[Calendar API v3] Delete a calendar event

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>"
    },
    "name": "calendar_v3_delete_event"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	ID of the event to delete
`calendar_id`	No	ID of the calendar containing the event (defaults to 'primary')	primary

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 6, 2026

TDQS

C2.9/5.0

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. It states the tool deletes an event, implying a destructive mutation, but fails to mention critical aspects like permissions required, whether deletion is permanent or reversible, rate limits, or error handling. This leaves significant gaps for an agent to understand the tool's behavior.

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 no wasted words. It front-loads the key information (API context and action) and is appropriately sized for a simple delete operation, making it easy to parse quickly.

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 tool's complexity (a destructive mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits (e.g., permanence, auth needs), expected outcomes, or error cases, which are crucial for safe and effective use by an AI agent.

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 input schema has 100% description coverage, fully documenting both parameters (event_id and calendar_id with its default). The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 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'), with the API version context ('Calendar API v3') providing specificity. However, it doesn't distinguish this tool from its siblings like 'calendar_v3_move_event' or 'calendar_v3_update_event' in terms of purpose, which prevents a perfect score.

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 is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., needing an existing event ID) or compare to siblings like 'calendar_v3_move_event' for moving instead of deleting. The description lacks any context for usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.