Skip to main content
Glama
Podcast MCP
by calebn

play_pending_preview_tool

Preview a pending remove or mute edit as current, suggested, or A/B full mix before approving, without changing the project.

Instructions

Hear Current vs Suggested vs A/B full mix for a pending remove or mute.

Suggested renders the window after approving the edit on a snapshot: the same ripple, paced pad, fades and mute that approving ships. Splits have no Suggested side. pad_sec is the audio either side of the edit, 0 to 10 seconds (default 0.5); outside that range it is refused with pending_preview_pad_out_of_range. Does not mutate the project.

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": {
      "edit_id": "<edit_id>"
    },
    "name": "play_pending_preview_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNosuggested
dry_runNo
edit_idYes
gap_secNo
pad_secNo
rerenderNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
    • removedInput schema / properties / source
      Removed value: -{
      -  "default": "premix",
      -  "title": "Source",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "project_path",
      -  "edit_id"
      -]New value: +[
      +  "edit_id"
      +]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does reasonably well: it explicitly states 'Does not mutate the project,' explains that Suggested renders the post-approval window on a snapshot with the same ripple/pad/fades/mute that approving ships, and names the refusal code 'pending_preview_pad_out_of_range' for out-of-range pad values. It stops short of covering permissions, cost/latency of rendering, or what rerender actually triggers.

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?

The purpose leads, followed by the semantics of Suggested and then the parameter constraint — a sensible front-loaded order with little padding. Minor waste from the doubled backticks and an odd line-wrapped layout, but no sentence is filler.

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 needn't be described, and the non-mutation plus snapshot semantics cover the biggest risks. Still, a 7-parameter tool with zero schema coverage and no annotations needs more on the four undocumented knobs (gap_sec, rerender, dry_run, project_path) before an agent can call it confidently outside the default path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description must compensate and only partly does. It thoroughly documents pad_sec (range 0-10s, default 0.5, refusal behavior) and sketches the mode values, but gap_sec, rerender, dry_run, project_path, and edit_id's expected format are left entirely unexplained.

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 states a specific verb and resource — hearing Current vs Suggested vs A/B full mix for a pending remove or mute — which is far more precise than a title restatement. It implicitly distinguishes itself from generic playback siblings by tying the audio to a pending edit, though it never names an alternative tool outright.

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?

Usage is scoped to 'a pending remove or mute,' and one exclusion is given ('Splits have no Suggested side'), which is genuinely useful. However, with siblings like play_ab_tool, play_compare_tool, and preview_inaudible_cut_tool present, the definition never says when to pick this tool over those, leaving routing to inference.

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