Skip to main content
Glama
nmbrthirteen

podcli

by nmbrthirteen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

modify_clip

Adjust a suggested clip's timing, title, caption style, or hook before export. Delete clips with action='delete'.

Instructions

Adjust a suggested clip before exporting. Change timing, title, caption style, or opening hook. Use action='delete' to remove a clip entirely. Reference clips by clip_number (from get_ui_state).

Input Schema

NameRequiredDescriptionDefault
indexNo0-based index (deprecated, use clip_number)
actionNoAction: 'update' (default) or 'delete'update
clip_idNoUUID of the clip (alternative to clip_number)
updatesNoPartial fields to update on the clip (ignored when action='delete')
clip_numberNoClip number (1-based, from get_ui_state)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • addedInput schema / properties / updates / properties / hook
      Added value: +{
+  "anyOf": [
+    {
+      "description": "Opening hook: a 1-15s passage from inside the clip, played before the clip. It must be a line actually spoken inside the clip's range (or its segments), never invented text.",
+      "properties": {
+        "end": {
+          "description": "Hook end in seconds, on the source clock",
+          "type": "number"
+        },
+        "mode": {
+          "description": "repeat: the passage plays first and again in place. move: it plays first and is cut from its place.",
+          "enum": [
+            "repeat",
+            "move"
+          ],
+          "type": "string"
+        },
+        "start": {
+          "description": "Hook start in seconds, on the source clock",
+          "type": "number"
+        }
+      },
+      "required": [
+        "start",
+        "end",
+        "mode"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Set the opening hook, or pass null to clear it."
+}
  2. Changed3 schema fields changedv2.7.3
    • addedInput schema / properties / updates / properties / context_line
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / updates / properties / payoff
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / updates / properties / standalone
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changedv2.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / updates / additionalProperties
      Removed value: -false
  4. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that action='delete' removes a clip entirely and that adjustments happen before exporting, but it omits permissions, reversibility, whether updates are partial, and what happens to unspecified fields.

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?

Four short sentences, front-loaded with the purpose and key actions. Every sentence contributes useful information about scope, editable fields, deletion, and clip reference without padding.

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?

Given the rich nested schema and no output schema, the description supplies enough to select and invoke the tool: it names the resource, editable aspects, delete action, and clip reference. It leaves some behavioral context unstated, but the schema covers parameter details well.

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%, so the baseline is 3. The description adds minor value by mentioning clip_number and action='delete', but largely repeats what the schema already documents in detail, including the nested updates fields.

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?

The description uses a specific verb ('Adjust') and resource ('a suggested clip'), and scopes it to 'before exporting'. It clearly distinguishes adjustment from creation or suggestion, but does not explicitly name or contrast sibling tools such as toggle_clip or create_clip.

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

Usage Guidelines3/5

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

It provides implied context ('before exporting') and a specific use for action='delete', but gives no explicit guidance on when to choose this tool over alternatives like toggle_clip, create_clip, or suggest_clips. The when-to-use is inferable but not spelled out.

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