calendar-mcp

Overview Schema Source Related Servers Discussions Admin

Delete an event

delete_event

DestructiveIdempotent

Permanently remove a specified calendar event. Optionally notify attendees about the cancellation, and confirm before deleting if supported.

Instructions

Permanently delete an event. This cannot be undone.

Clients that support elicitation are asked to confirm first; if the user declines, nothing is deleted and deleted comes back false.

Args: event_id: The event to delete (from find_events). calendar_id: Calendar the event lives on. send_notifications: Whether Google emails the attendees that it was cancelled. Default true. account: Account name from 'calendar-mcp accounts'; omit for the default.

Input Schema

TableJSON Schema

Name	Required	Default
`account`	No
`event_id`	Yes
`calendar_id`	No	primary
`send_notifications`	No

Output Schema

TableJSON Schema

Name	Required	Description
`deleted`	Yes	True when the event was removed.
`message`	No	One-line human-readable summary of what happened.
`event_id`	Yes	ID of the deleted event.
`calendar_id`	Yes	Calendar the event was on.
`confirmed_by_user`	No	True/False when the client answered a confirmation prompt; null when the client does not support elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Sep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations (destructiveHint), the description discloses irreversible deletion, confirmation elicitation behavior, and the 'deleted' false outcome when declined. This gives the agent important behavioral expectations not present in the structured metadata.

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 tightly written: the irreversible-destruction warning is front-loaded, the elicitation caveat is a single sentence, and the parameter list is scannable. Every sentence adds information.

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

Completeness5/5

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

Given the annotations, output schema, and sibling list, the description covers purpose, side effects, confirmation behavior, notification defaults, and account selection. No critical information for calling this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the Args section documents all four parameters with meaning: event_id originates from find_events, calendar_id defaults to primary, send_notifications controls attendee emails and defaults true, and account is sourced from calendar-mcp accounts. This compensates fully for the schema gap.

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?

The description opens with a specific verb and resource: 'Permanently delete an event.' It clearly distinguishes this from siblings like update_event and move_event, and the permanence warning adds specificity beyond the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended context is clear: use this when an event should be permanently removed, with calendar_id and account specifying target. It does not explicitly name alternatives or exclusion conditions, but the resource scope is unambiguous.

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