Skip to main content
Glama

effect_auto_duck

Automatically lowers background music volume when narration or other audio is detected, ensuring clear speech over music in podcasts and videos.

Instructions

Auto Duck: automatically reduce volume when audio is detected on another track. Place the control track (e.g. narration) above the track to duck (e.g. music). Select the track to duck before running.

Args: duck_amount_db: How much to reduce volume in dB (-24 to 0). Default: -12 inner_fade_down_len: Inner fade down length in seconds (>= 0). Default: 0 inner_fade_up_len: Inner fade up length in seconds (>= 0). Default: 0 outer_fade_down_len: Outer fade down length in seconds (>= 0). Default: 0.5 outer_fade_up_len: Outer fade up length in seconds (>= 0). Default: 0.5 threshold_db: Threshold for duck trigger in dB (-100 to 0). Default: -30 maximum_pause: Maximum pause between ducking regions in seconds (>= 0). Default: 1.0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
duck_amount_dbNo
inner_fade_down_lenNo
inner_fade_up_lenNo
outer_fade_down_lenNo
outer_fade_up_lenNo
threshold_dbNo
maximum_pauseNo
Behavior3/5

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

With no annotations provided, the description carries the full burden. It explains the detection logic and track ordering requirements, but fails to disclose whether the operation is destructive (modifies audio data), creates automation envelopes, or is reversible via undo.

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?

The description is well-structured with purpose first, followed by workflow and parameters. While the Args section is lengthy, this verbosity is necessary given the schema's lack of descriptions; no sentences are redundant.

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

Completeness3/5

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

The description adequately covers input parameters and setup requirements for this 7-parameter tool, but leaves gaps regarding execution results (return values, success indicators, or modified track state) given the absence of an output schema.

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?

Given 0% schema description coverage, the Args section comprehensively compensates by documenting all 7 parameters with semantic meaning (e.g., 'How much to reduce volume'), valid ranges (-24 to 0), units (dB, seconds), and default values.

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?

The description clearly states the tool 'automatically reduce[s] volume when audio is detected on another track,' specifying the sidechain ducking behavior. The examples (narration over music) help distinguish it from generic volume effects like effect_amplify or effect_fade_out.

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?

It provides specific workflow prerequisites ('Place the control track... above the track to duck,' 'Select the track... before running') but lacks explicit guidance on when to choose this over alternatives like effect_crossfade_tracks or manual envelope editing.

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/xDarkzx/Audacity-MCP'

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