Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_bleed_suppression_tool

Suppress mic-bleed words in podcast multitrack projects, with dry-run previews to review edits before applying.

Instructions

Suppress mic-bleed words (dry_run previews without applying).

Input Schema

NameRequiredDescriptionDefault
applyNo
wordsNo
dry_runNo
end_secNo
speakerNo
track_idNo
start_secNo
project_pathNo
exclude_wordsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / exclude_words
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Exclude Words"
+}
    • removedInput schema / properties / exclude_words_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Exclude Words Json"
-}
    • 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"
    • addedInput schema / properties / words
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Words"
+}
    • removedInput schema / properties / words_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Words Json"
-}
    • removedInput schema / required
      Removed value: -[
-  "project_path"
-]
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only discloses the dry_run preview path. It says nothing about permissions, whether suppression is reversible, what happens to matched words, or how 'apply' and 'dry_run' interact - a substantial gap for a 9-parameter 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?

A single front-loaded sentence with no filler, so there is no waste to trim. Its brevity is only a virtue relative to the space it uses; the tool clearly needs more content, but that is a completeness problem, not a conciseness one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists so return values need not be described, but with 9 undocumented parameters, no annotations, and no usage routing, the definition is far too thin for a destructive-sounding suppression operation. An agent would have to guess at required inputs and the effect of the apply/dry_run flags.

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

Parameters1/5

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

Schema coverage is 0% across 9 parameters, so the description must compensate and does not. It never explains words, exclude_words, speaker, track_id, project_path, or start_sec/end_sec, nor clarifies the apparently overlapping 'apply' (default true) and 'dry_run' (default false) switches.

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+resource combination ('Suppress mic-bleed words') that identifies the operation clearly. However, it does not distinguish itself from close siblings such as bleed_words_tool (likely detection/listing) or apply_low_audibility_suppression_tool, so an agent cannot confidently route between them on this text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the parenthetical about dry_run previewing, which is really a parameter note. There is no statement of when to use this versus bleed_words_tool, apply_transcript_gate_tool, or mute_off_speaker_tool, and no prerequisites such as needing bleed words identified first.

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