Skip to main content
Glama
Podcast MCP
by calebn

kit_apply_tool

Apply all segments from a podcast kit to an episode in order, with a dry run to preview each insertion's effect and duration before writing changes.

Instructions

Put every segment of a kit on an episode, in order (podcast kit apply).

Each entry is an InsertSegment on the document plane (journaled, shown in Studio, later content ripples), so end means the end after the earlier entries. There is no compound command: every entry is its own undo step, undo_steps in the result says how many. Use dry_run=true first: it runs the whole kit on a copy, reports each entry's effect and the new duration, and changes nothing (not even a legacy project rename). An unknown kit, a segment or pinned version missing from the library, changed segment audio and any refusal the copy run finds are reported before anything is written. A failure of the write itself (disk, lock, conflict) can still stop the apply after earlier entries went in; the error then names the entry and how many were applied, and each applied entry is its own undo step. Errors: kit_unknown, kit_segment_missing, segment_hash_mismatch, segment_position_out_of_range, segment_media_invalid, segment_write_failed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kit_id": "<kit_id>"
    },
    "name": "kit_apply_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_idYes
dry_runNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that each entry is a journaled InsertSegment visible in Studio, that there is no compound undo (one undo step per entry, counted in undo_steps), that dry_run operates on a copy and mutates nothing, that preconditions are validated before writing, and that a mid-write failure leaves earlier entries applied and names the failing entry and count.

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 line, then behavior, then error taxonomy in a compact list. Dense but almost every sentence carries new information; the RST-style double backticks and parenthetical asides add minor noise.

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?

For a mutating, multi-entry apply with no annotations, the description covers atomicity, undo granularity, dry-run semantics, failure recovery, and the full error code set. The output schema exists so return shape needn't be explained, but the unexplained project_path parameter is a real remaining gap.

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% across three parameters. The description thoroughly explains dry_run (runs the whole kit on a copy, reports per-entry effect and new duration, changes nothing) and hints at kit_id semantics via kit_unknown/kit_segment_missing errors, but project_path is never mentioned, so one of three parameters remains undefined in both schema and prose.

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?

States a specific verb and resource ('Put every segment of a kit on an episode, in order') plus the CLI equivalent, and the ordering semantics distinguish it from sibling kit tools like kit_show_tool or kit_list_tool, which cannot perform an ordered multi-segment write.

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?

Gives explicit operational guidance: run with dry_run=true first, and explains what that trial run reports. It does not, however, contrast itself with other apply_* siblings (apply_edit_plan_tool, apply_suggested_actions_tool), so the agent must infer that this tool is the kit-specific one.

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