Podcast MCP

Overview Schema Source Related Servers Discussions Admin

shorten_gaps_tool

Shorten word gaps longer than max_gap_sec across a multitrack podcast timeline, ripple dialogue tracks, and require confirmation when another speaker's audio would be cut.

Instructions

Shorten word gaps longer than max_gap_sec across the timeline.

Each shortened pause ripples every dialogue track; another speaker talking in a pause needs confirmation. A ripple that cuts another track's speech stays unchanged until you repeat with override_audio_checks=true (recorded).

Input Schema

Name	Required	Description	Default
`max_gap_sec`	No
`project_path`	No
`use_inaudible_opt`	No
`override_audio_checks`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.1Oct 19, 2026
- addedInput schema / properties / override_audio_checks
```
Added value: +{
+  "default": false,
+  "title": "Override Audio Checks",
+  "type": "boolean"
+}
```
- 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 / required
```
Removed value: -[
-  "project_path"
-]
```
First observedv0.1.0Sep 20, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that each shortened pause ripples every dialogue track, that overlapping speech triggers a confirmation gate, and that the ripple is blocked (and recorded) until override_audio_checks=true. It leaves unclear whether the confirmation is interactive or returned in the response.

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?

Three tight sentences with the core action front-loaded and the ripple/override caveat following. Dense but each sentence earns its place; no filler.

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?

An output schema exists, so return values need not be described. Given a rippling mutation tool with no annotations, the description covers the risky side effects well. Gaps remain around the undocumented use_inaudible_opt and project_path parameters.

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 coverage is 0%, so the description must compensate. It explains max_gap_sec's role (the threshold) and override_audio_checks' effect, but project_path and use_inaudible_opt are never mentioned, leaving half the parameters undocumented in both schema and prose.

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: shorten word gaps longer than max_gap_sec across the timeline. An agent understands the operation immediately. It does not distinguish itself from the closely related sibling strip_silence_tool, so it stops short of a 5.

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?

Implies usage through behavior: a pause containing another speaker's talk needs confirmation, and a ripple that would cut speech requires repeating with override_audio_checks=true. That is conditional guidance, but there is no statement of when to prefer this over strip_silence_tool or insert_gap_tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server