TimeTree MCP Server

update_event_comment

DestructiveIdempotent

Replace the text of an existing TimeTree event comment using its comment ID; only the comment author can edit it, so retrieve the ID first.

Instructions

Replace the text of an existing comment and return it. TimeTree lets only the comment's author edit it. Get comment_id from list_event_comments; use add_event_comment to post a new comment instead.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	Yes	New comment content
`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
`comment`	Yes
`message`	No
`success`	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": {
+    "comment": {
+      "properties": {
+        "author_id": {
+          "description": "User ID of the author",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "author_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "calendar_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "content": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "editor_id": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "event_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "comment_id for update_event_comment and delete_event_comment",
+          "type": "string"
+        },
+        "images": {
+          "items": {
+            "properties": {
+              "filename": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "height": {
+                "type": [
+                  "number",
+                  "string",
+                  "null"
+                ]
+              },
+              "image_index": {
+                "minimum": 0,
+                "type": "integer"
+              },
+              "width": {
+                "type": [
+                  "number",
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "image_index",
+              "filename",
+              "width",
+              "height"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "updated_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "content",
+        "images"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "comment"
+  ],
+  "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.5/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely new context by disclosing the author-only restriction and clarifying that the operation fully replaces the text rather than appending. It does not describe failure modes or what happens to prior content beyond replacement, so it falls just short of a 5.

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 earning its place: what it does, the permission constraint, and the disambiguation from siblings. The core operation is front-loaded.

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?

An output schema exists, so return values need no explanation; the description covers the mutation's scope, the auth prerequisite, and the sibling alternatives. Nothing an agent needs in order to call this correctly is missing.

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%, and the description repeats the comment_id provenance that the schema already documents ("The comment id from list_event_comments"). No additional semantics (e.g., content length limits, formatting) are added, 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?

"Replace the text of an existing comment and return it" gives a precise verb, resource, and effect, and the description explicitly distinguishes itself from add_event_comment (create) and list_event_comments (source of the id). An agent can route between the three comment tools without opening a 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?

It states both the prerequisite ("Get comment_id from list_event_comments") and the alternative for the opposite operation ("use add_event_comment to post a new comment instead"). It also names the permission constraint ("only the comment's author edit it"), which tells the agent when this call will fail.

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