gsuite

google-calendar_delete_event

Delete a Google Calendar event by providing the calendar ID and event ID. Optionally send notifications to attendees.

Instructions

Deletes an event. Returns 204 No Content with empty body on success.

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": {
      "calendarId": "<calendarId>",
      "eventId": "<eventId>"
    },
    "name": "google-calendar_delete_event"
  }
}

Input Schema

Name	Required	Description
`eventId`	Yes	Event identifier
`calendarId`	Yes	Calendar identifier. Use 'primary' for the primary calendar
`sendUpdates`	No	Whether to send notifications to attendees (all, externalOnly, none)
`sendNotifications`	No	Whether to send notifications about the deletion

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Jul 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, description provides some behavioral info (returns 204 No Content with empty body). But lacks disclosure on permanence, notifications, permissions, or recurring event handling. The parameters sendUpdates and sendNotifications are not discussed in 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?

Extremely concise (2 sentences), front-loaded with action and response. No fluff or redundant information.

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

Completeness3/5

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

For a simple delete operation without output schema, description covers purpose and response. But lacks context like whether deletion is hard or soft, impact on recurring events, or permission requirements. Marginal completeness.

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?

All 4 parameters have schema descriptions (100% coverage). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose5/5

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

Clearly states the verb 'deletes' and resource 'event', and distinguishes from sibling tools like create, get, update by specifying delete action. Includes response details, no tautology.

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 on when to use vs alternatives (e.g., update event with status cancelled), no prerequisites or exclusions mentioned. Only states what it does.

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