Skip to main content
Glama

delete_event

DestructiveIdempotent

Delete a calendar event by ID; for recurring events, choose one occurrence or all future ones, with confirmation required for irreversible future deletions.

Instructions

Delete an event. For a recurring event, 'span' chooses one occurrence or all later ones. The result has a copy of the event, so create_event can put it back. Deleting all later occurrences needs 'confirm' true.

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": {
      "id": "<id>"
    },
    "name": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent id from list_events, search_events or get_event. Recurring events have an id with an @ part. Use it as given.
spanNoFor a recurring event: 'this' changes only this occurrence (default), 'future' changes this and all later ones.
confirmNoMust be true to delete a recurring event with 'span' 'future'. It cannot be undone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true. The description adds useful behavior beyond that: the result returns a copy of the event so create_event can restore it, and deleting all later occurrences requires 'confirm' true. It does not cover notification or permission side effects, but it materially improves transparency for a destructive action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded: it states the action first, then the recurring-event distinction, then recovery and confirmation constraints. Every sentence contributes useful information, though the wording could be slightly tighter.

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

Completeness4/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 output schema, the description covers the critical behaviors: recurrence scoping, confirmation before deleting future occurrences, and the availability of a copy for restoration via create_event. It is complete enough for correct invocation, with only minor gaps around side effects such as attendee notifications.

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%, so all three parameters are already documented in the input schema. The description restates the 'span' choices and 'confirm' requirement but adds little parameter meaning beyond what the schema already provides; 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?

The description opens with a specific verb and resource: 'Delete an event.' It also distinguishes the recurring-event case and mentions create_event as the restore path, making the tool's scope clear without needing to inspect the schema.

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

Usage Guidelines3/5

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

It gives guidance for recurring events: 'span' selects one occurrence or all later ones, and 'confirm' is required for deleting all later occurrences. However, it does not explicitly state when to use this versus update_event, get_event, or delete_calendar, so broader usage guidance is only implied.

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