Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Remove Calendar Event

ha_config_remove_calendar_event
DestructiveIdempotent

Delete a calendar event from Home Assistant by specifying the calendar entity ID and event UID. Supports deleting single events and recurring occurrences.

Instructions

Delete an event from a calendar.

Deletes a calendar event via the WebSocket calendar/event/delete command. HA's calendar component only registers create_event and get_events as REST services — delete and update live on the WebSocket API only. Get the event UID from ha_config_get_calendar_events().

EXAMPLES:

  • Delete a single event: ha_config_remove_calendar_event("calendar.family", uid="event-12345")

  • Delete one occurrence and all later ones: ha_config_remove_calendar_event("calendar.work", uid="recurring-event-67890", recurrence_id="20240115T100000", recurrence_range="THISANDFUTURE")

If a Claude Desktop user gets a 4-minute timeout with no result on this call, read the target back before repeating it, and tell them to wait a few seconds before clicking the manual-approve button, as clicking it too quickly is known to cause hangs in Claude Desktop. This workaround is specific to Claude Desktop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesUnique identifier of the event to delete
entity_idYesCalendar entity ID (e.g., 'calendar.family')
recurrence_idNoRecurrence ID for recurring events
recurrence_rangeNoRecurrence range: 'THISANDFUTURE' to delete this and future occurrences. Home Assistant compares this value verbatim, so no other spelling (including 'THIS_AND_FUTURE') selects the range.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv8.6.0
    • changedInput schema / properties / recurrence_id / description
      Previous value: -"Optional recurrence ID for recurring events"New value: +"Recurrence ID for recurring events"
    • changedInput schema / properties / recurrence_range / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "const": "THISANDFUTURE",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / recurrence_range / description
      Previous value: -"Optional recurrence range ('THIS_AND_FUTURE' to delete this and future occurrences)"New value: +"Recurrence range: 'THISANDFUTURE' to delete this and future occurrences. Home Assistant compares this value verbatim, so no other spelling (including 'THIS_AND_FUTURE') selects the range."
  2. First observedv7.14.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructive/idempotent/readOnly=false, but the description adds real operational context beyond them: the fact that delete lives only on the WebSocket API (no REST fallback), that recurrence_range is matched verbatim, and a known Claude Desktop timeout/hang workaround. These are exactly the traits annotations cannot express.

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 purpose, then implementation rationale, examples, and the desktop workaround in a logical order. The implementation explanation is slightly long, but each section earns its place by preventing misuse.

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?

Covers the API path, prerequisite for obtaining the uid, examples per use case, recurring-event semantics, and a known failure mode. With an output schema present, return-value explanation is unnecessary, leaving nothing material missing for correct invocation.

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 100%, so baseline is 3, but the description adds meaning by showing how uid pairs with recurrence_id and recurrence_range in real calls and where the uid comes from. It does not add much beyond the schema for recurrence_range, which the schema already documents as verbatim.

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?

States a specific verb+resource ('Delete an event from a calendar') and clarifies the exact command path (WebSocket calendar/event/delete). It also distinguishes itself from siblings by pointing at ha_config_get_calendar_events() as the source of the UID, so an agent can tell it apart from the get/set calendar tools.

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?

Gives a clear prerequisite (obtain the uid from ha_config_get_calendar_events) and concrete examples for both single-event and recurring-range deletion. It does not explicitly state when NOT to use it, but the usage path is unambiguous.

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

Deploy Server

Other Tools