Skip to main content
Glama
langmail-mcp

langmail-mcp

Official
by langmail

Delete calendar event

delete_calendar_event
Destructive

Delete or cancel a calendar event you organize by uid and notify attendees, or cancel one occurrence of a recurring series by recurrenceId while keeping the rest.

Instructions

Cancel, delete or remove a calendar event or meeting the user organizes, identified by its uid from create_calendar_event or list_calendar_events, and send iMIP cancellations to its attendees. (To decline an invitation someone else sent, use respond_to_event instead.) By default this deletes the ENTIRE event — for a recurring event that means every occurrence. To instead cancel ONE occurrence of a recurring series (e.g. skip this week’s standup), pass recurrenceId naming that occurrence by its original start; the master rule and every other occurrence stay unchanged. Defaults to the user’s default calendar; pass calendarUrl if the event lives in another calendar.

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": {
      "uid": "<uid>"
    },
    "name": "delete_calendar_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
calendarUrlNo
recurrenceIdNoOptional ISO 8601 instant that scopes this deletion to a single occurrence of a recurring series, identified by that occurrence’s original start (e.g. 2026-06-16T10:00:00Z), or its date for an all-day series (2026-06-16). When set, only that one occurrence is cancelled — the master rule and every other occurrence stay exactly as they are — and attendees get a cancellation scoped to just that instance. The instant must land on an actual occurrence of the series. Omit to delete the whole event (for a recurring event, the entire series).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: it sends iMIP cancellations to attendees, and by default it removes the ENTIRE recurring series rather than one occurrence. It stops short of stating permission requirements or irreversibility, but the side-effect disclosure is the critical piece an agent needs.

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?

Front-loads the action, then the sibling exclusion, then the whole-series vs single-occurrence distinction in descending order of importance. Slightly long as a single dense paragraph, but nearly every clause carries decision-relevant 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?

There is no output schema and only three parameters, one required, and the description covers the destructive scope, attendee notification, calendar targeting, and recurrence scoping. Nothing an agent needs in order to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is only 33%, so the description must compensate, and it largely does: calendarUrl gets a clear conditional ('pass calendarUrl if the event lives in another calendar') and uid is given provenance (from create_calendar_event or list_calendar_events). The recurrenceId explanation repeats most of what the schema already documents, adding marginal value but no harm.

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?

Uses three concrete verbs (cancel/delete/remove) against a specific resource (calendar event or meeting the user organizes) and immediately differentiates from siblings by naming respond_to_event for declines and citing create_calendar_event/list_calendar_events as the source of the uid. An agent can identify the operation and its scope without opening 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 Guidelines5/5

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

Explicitly states the negative case in a parenthetical: to decline someone else's invitation, use respond_to_event instead. It also gives the decision rule for the whole-series vs single-occurrence case with a concrete example (skip this week's standup), so the most error-prone choice is fully disambiguated.

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