Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bounce_audio_tool

Export selected or all podcast stems to export/bounces/ without mastering, with optional start/end times and formats. Omit track IDs to bounce all non-muted mixable tracks.

Instructions

Bounce selected (or all) stems to export/bounces/ without mastering.

Times are timeline seconds. track_ids lists the stems, or omit for all non-muted mixable tracks. formats lists extensions (e.g. ["wav", "mp3"]); default wav only.

Input Schema

NameRequiredDescriptionDefault
end_sNo
formatsNo
start_sNo
track_idsNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / formats
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Formats"
+}
    • removedInput schema / properties / formats_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Formats 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 / track_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Track Ids"
+}
    • removedInput schema / properties / track_ids_json
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Track Ids Json"
-}
    • removedInput schema / required
      Removed value: -[
-  "project_path"
-]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations the description carries the full burden. It discloses useful behavior: output goes to export/bounces/, no mastering is applied, and unset track_ids/formats default sensibly. It is silent on overwrite behavior, whether files are written or merely staged, permission requirements, and any side effects on the session.

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 short, front-loaded sentences with no filler; the core action and destination come first, then defaults. Slightly terse on the time parameters' purpose but nothing is wasted.

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

Completeness5/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 no explanation, and the description covers the action, destination, selection rules, and format defaults. For a 5-param export tool the remaining gaps (project_path, overwrite behavior) are minor.

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 clarifies track_ids (stem list, omission semantics) and formats (extension list, wav default) and gives units for the time bounds ('times are timeline seconds'). It says nothing at all about project_path, leaving one of five parameters fully 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+resource ('Bounce ... stems') plus scope ('selected (or all)') and a distinguishing qualifier ('without mastering') and destination ('export/bounces/'). It implicitly separates itself from render_final/export_audio_tool via the no-mastering note, but doesn't name any sibling explicitly.

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 one concrete selection rule ('omit for all non-muted mixable tracks') and a default for formats, which is real usage guidance. However it never says when to prefer this over export_audio_tool, render_final, or render_preview, so the routing decision is left 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