Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_clips_tool

Move podcast clips along the timeline or to another track without shifting neighboring clips or cutting all dialogue lanes. Supports inter-track moves while keeping original media.

Instructions

Move clips in session time and/or onto another track (no neighbor ripple).

clips is a list of {clip_id, timeline_start, track_id}. Inter-track moves keep the originating media via source_id. Unlike move_segment_tool, this does not cut a range on every dialogue lane.

Input Schema

NameRequiredDescriptionDefault
clipsYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / clips
      Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Clips",
+  "type": "array"
+}
    • removedInput schema / properties / clips_json
      Removed value: -{
-  "title": "Clips Json",
-  "type": "string"
-}
    • 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"
    • changedInput schema / required
      Previous value: -[
-  "project_path",
-  "clips_json"
-]New value: +[
+  "clips"
+]
  2. First observedv0.1.0

TDQS

A3.8/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 burden, and it does disclose meaningful traits: no neighbor ripple, inter-track moves retaining originating media via source_id, and not cutting a dialogue-lane range. However it says nothing about reversibility, session/auth prerequisites, or whether the move is destructive, leaving real gaps for a mutation tool.

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?

Purpose is front-loaded in the first sentence, followed by tightly packed supporting detail on structure and sibling differentiation. No padding, though the backtick-heavy formatting is slightly noisy.

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, and the description covers the required parameter's shape and key behavioral contrasts. It remains incomplete on project_path semantics and on mutation safety/reversibility, which matters given zero annotations.

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 0%, so the description must compensate. It usefully documents the required clips item shape as {clip_id, timeline_start, track_id}, but the project_path parameter is left completely unexplained, so coverage is only partial.

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 opening sentence gives a specific verb ('Move') and resource ('clips') plus scope ('in session time and/or onto another track'), and explicitly distinguishes itself from move_segment_tool. An agent can identify the tool's role and its key contrast with the sibling without opening any schema.

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 names an alternative (move_segment_tool) and states the behavioral difference ('does not cut a range on every dialogue lane'), which implies when to prefer this tool. It stops short of an explicit 'use this when / use that when' rule, but the routing signal is clear.

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