TimeTree MCP Server

delete_event

DestructiveIdempotent

Permanently deletes a TimeTree event, including all occurrences of a recurring event, to remove an entire event series.

Instructions

Delete an event, including every occurrence of a recurring event. Cannot be undone. To delete one occurrence or the ones after it, use delete_event_occurrence. For memos use delete_memo.

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

Input Schema

Name	Required	Description	Default
`event_uuid`	Yes	The UUID of the event to delete (from get_events)
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)

Output Schema

Name	Required	Description	Default
`message`	No
`success`	Yes
`deleted_event_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deleted_event_uuid": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "deleted_event_uuid"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.4.0Oct 3, 2026

changedInput schema / properties / calendar_id / description

Previous value: -"The calendar ID"New value: +"The calendar ID from list_calendars (numeric string; numbers are also accepted)"

changedInput schema / properties / calendar_id / type
```
Previous value: -"number"New value: +"string"
```

First observedv0.3.0May 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Cannot be undone' is reinforcing rather than new. The genuinely additive piece is the series-wide deletion scope ('including every occurrence of a recurring event'), which an agent would not infer from annotations alone. It does not mention permissions or whether the event must belong to the given calendar.

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?

Three short sentences, front-loaded with the destructive scope, then irreversibility, then the alternatives. No wasted text and ordering prioritizes what matters most.

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?

Output schema exists and parameters are fully documented, so the description only needs to convey scope and alternatives, which it does well. The only real gap is any precondition tying event_uuid to calendar_id for a destructive call.

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 coverage is 100% and both parameters carry descriptions pointing to get_events and list_calendars as sources. The description adds no syntax or constraint detail beyond that, so baseline 3 applies.

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?

Specific verb plus resource ('Delete an event') with an explicit scope qualifier: every occurrence of a recurring event. It also names the two sibling tools it must not be confused with (delete_event_occurrence, delete_memo), so an agent can distinguish it without opening schemas.

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?

Explicit routing: single-occurrence or following-occurrence deletion goes to delete_event_occurrence, and memo deletion goes to delete_memo. The implied default (whole event/series) is unambiguous by contrast.

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