Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audition_context_tool

Captions dialogue tracks in a timeline window, returning comments, effects, prosody, and clip-skew details for podcast audition without playing audio.

Instructions

Caption each dialogue track in a timeline window + clip-skew / render freshness.

detail: summary (default) includes comments, active effects, edits, and windowed hum/clip hypotheses; full expands edit/comment payloads; visual adds waveform/spectrogram PNGs (slower). Returns audition_context.v2 (typed hypotheses, suggested_listen, explicit clocks). Each track also carries a prosody window (pitch, rate, energy, prominent words, phrase boundaries) read from the pipeline's cached profile (analyze_prosody step); status is missing/stale with a hint when no fresh profile is cached yet, or unavailable (redacted error) when the cache cannot be read. Top-level prosody_notes has up to 8 one-line summaries. Times are timeline (session) seconds. Does not play audio.

Input Schema

NameRequiredDescriptionDefault
detailNosummary
end_secYes
start_secYes
project_pathNo
skew_warn_secNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • changedInput schema / required
      Previous value: -[
-  "project_path",
-  "start_sec",
-  "end_sec"
-]New value: +[
+  "start_sec",
+  "end_sec"
+]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does so well: it discloses the three detail modes and their cost tradeoff, the prosody profile status values (missing/stale/unavailable with redacted error), time units, and explicitly that it does not play audio. It stops short of discussing permissions or latency beyond the 'visual' hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and organizes detail modes legibly, but the sentence 'Caption each dialogue track in a timeline window + clip-skew / render freshness' is compressed to the point of ambiguity and the overall block is dense with inline code spans.

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 complex tool with 5 params, no annotations, and an existing output schema, the description covers detail modes, prosody statuses, and clock semantics, so an agent can call it confidently. The main gap is the unexplained project_path/skew_warn_sec params.

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 thoroughly explains `detail` and the timeline semantics of start_sec/end_sec, and 'clip-skew' gestures at skew_warn_sec, but `project_path` and the numeric meaning of skew_warn_sec remain undocumented.

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 and resource: captioning each dialogue track over a timeline window, with clip-skew and render-freshness attributes. An agent can distinguish it from context siblings like build_edit_context, though the jargon ('caption', 'clip-skew') blurs it slightly.

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?

Gives useful mode-selection guidance for the `detail` parameter (summary/full/visual, with 'visual' noted as slower), which is a form of when-to-use. However it never routes the agent against alternatives such as build_edit_context or get_session_state_tool, and states no preconditions, so context is only implied.

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