Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_comment_tool

Modify a comment's body, associated tracks, or timeline start and end anchors by ID. Set track_ids to an empty list to make the comment session-wide; omit it to keep existing tracks.

Instructions

Update comment body, tracks, and/or timeline anchor. Times are timeline seconds.

track_ids=[] makes the comment session-wide; omit it to keep the tracks.

Input Schema

NameRequiredDescriptionDefault
bodyNo
track_idsNo
comment_idYes
project_pathNo
timeline_endNo
timeline_startNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • addedInput schema / properties / track_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Track Ids"
+}
    • removedInput schema / properties / track_ids_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Track Ids Json"
-}
    • changedInput schema / required
      Previous value: -[
-  "project_path",
-  "comment_id"
-]New value: +[
+  "comment_id"
+]
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses that track_ids=[] makes the comment session-wide, a non-obvious mutation effect, but says nothing about permissions, reversibility, or what happens to fields left unset (partial vs full update).

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?

Two tight sentences, front-loaded with the core action and followed by the one genuinely surprising parameter rule. No filler; only the stray blank line mildly disrupts flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. But for a 6-parameter mutation tool with zero annotations and zero schema descriptions, the description covers only the trickiest parameter and leaves the rest under-specified.

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 0%, so the description must compensate, and it does explain the semantics of track_ids=[] versus omission and clarifies that times are timeline seconds. However, project_path is left entirely unexplained and the body/timeline params get only naming-level coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Update) and resource (comment) and names the mutable facets: body, tracks, and timeline anchor. It distinguishes itself from add_comment_tool/delete_comment_tool by implication, but never explicitly contrasts with siblings like resolve_comment_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to reach for this tool versus resolve_comment_tool, set_comment_action_done_tool, or add_comment_reply_tool. The only conditional advice (omit track_ids to keep tracks) is parameter behavior, not tool-selection guidance.

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