Skip to main content
Glama

auto_cleanup_podcast

Clean up podcast audio with one click: applies DC offset removal, high-pass filter, noise reduction, compression, and safe loudness check. Runs in background and returns a job ID for monitoring.

Instructions

ONE-CLICK PODCAST CLEANUP: Professional broadcast-quality processing. Runs in background — returns a job_id immediately. Use check_pipeline_status to monitor. Safe for badly recorded audio — only reduces peaks if too hot, never boosts.

Pipeline: DC offset > HPF 80Hz > NR 12dB > compress 3:1 (30ms attack, 200ms release) > safe loudness check. Optional: noise reduction (on by default), silence truncation (off by default).

After the pipeline finishes, the user can manually apply LUFS normalization using the loudness_normalize tool if they want to hit a specific streaming target.

Args: remove_noise: Apply noise reduction using first 0.5s as noise profile. Default: True remove_silence: Truncate long silences/dead air. Default: False verify: Measure the audio before and after and report what changed. Costs two extra exports. Set False on very long projects.

IMPORTANT: If remove_noise is True, the first 0.5 seconds should be room tone / silence. DO NOT call this again if a pipeline is already running — use check_pipeline_status instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verifyNo
remove_noiseNo
remove_silenceNo
Behavior5/5

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

Despite no annotations, description fully discloses pipeline steps (DC offset, HPF, NR, compress, loudness check), safety behavior (only reduces peaks), and effects of verify parameter (costs two extra exports). Covers all key behavioral traits.

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?

Well-structured with front-loaded key info (one-click, background). Pipeline details are technical but justified. Slightly verbose in listing pipeline steps; could be more concise without losing value.

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?

Given no output schema and low complexity (3 boolean params), description covers purpose, usage, parameters, and behavioral details. Could mention exact return format of verify or job_id, but cross-references sibling tools adequately.

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

Parameters5/5

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

Schema has 0% description coverage, but description explains each parameter in detail: remove_noise uses first 0.5s noise profile, remove_silence truncates dead air, verify measures before/after and reports changes. Adds significant meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it's a podcast cleanup tool with broadcast-quality processing, using specific verb 'cleanup' and resource 'podcast'. It implicitly distinguishes from sibling auto_cleanup tools by specifying podcast context.

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

Usage Guidelines5/5

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

Explicitly states to use check_pipeline_status for monitoring, warns not to call again if pipeline is running, provides prerequisites for remove_noise (first 0.5s room tone), and mentions alternative loudness_normalize tool after pipeline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robworks-code/audacity-mcp-max'

If you have feedback or need assistance with the MCP directory API, please join our Discord server