TimeTree MCP Server

delete_event_comment

DestructiveIdempotent

Deletes a comment from a TimeTree event permanently; use it when you are the comment's author and have the comment ID from list_event_comments.

Instructions

Delete a comment from an event. Cannot be undone, and TimeTree lets only the comment's author delete it. Get comment_id from list_event_comments.

Input Schema

TableJSON Schema

Name	Required	Description
`comment_id`	Yes	The comment id from list_event_comments
`event_uuid`	Yes	The event UUID
`calendar_id`	Yes	The calendar ID from list_calendars (numeric string; numbers are also accepted)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Oct 22, 2026

changedInput schema / properties / comment_id / description

Previous value: -"The comment/activity ID"New value: +"The comment id from list_event_comments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "deleted_comment_id": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "deleted_comment_id"
+  ],
+  "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.2/5.0

Behavior4/5

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

The annotations already mark the tool as destructive and non-read-only, but the description adds important context not present there: the deletion cannot be undone and TimeTree restricts deletion to the comment's author. It could mention what happens on repeated deletion or permission failures, but the added behavioral context is substantial.

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, each with a clear purpose: the action, the destructive/permission behavior, and where to get the key parameter. Nothing is wasted.

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?

The tool has annotations covering destructiveness and an output schema, so the description does not need to explain return values. It completes the picture with irreversibility and author-only permission, though it does not describe failure behavior when the caller is not the author.

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 the schema already documents all three parameters, including that comment_id comes from list_event_comments. The description repeats this provenance for comment_id but adds no syntax or format details beyond the schema.

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 states a specific verb and resource: deleting an event comment. It clearly distinguishes this from sibling deletion tools like delete_event and delete_memo by naming the exact resource type.

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?

It gives clear prerequisites: the comment must be deleted by its author, and the comment_id should come from list_event_comments. It does not explicitly name alternatives, but the usage context is clear.

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