Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Label Regions Export

audacity_label_regions_export

Export all positive-duration regions in a label track as numbered audio files using the current mix and explicit time/track selections; point labels are skipped and existing outputs are refused.

Instructions

Export every positive-duration region in one label track as numbered audio files, using the current mix and explicit time/track selections. Point labels are skipped. Existing outputs are refused and all destinations are checked before export.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "directory": "<directory>"
    },
    "name": "audacity_label_regions_export"
  }
}

Input Schema

Name	Required	Default
`format`	No	wav
`channels`	No
`directory`	Yes
`trackName`	No	Labels

Output Schema

Name	Required	Description	Default
`count`	Yes
`files`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already indicate a non-read-only, non-idempotent, non-destructive, open-world operation. The description adds important behavior beyond them: point labels are skipped, existing outputs are refused, and destinations are checked before export.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences, front-loaded with the core export action. Every sentence supplies useful scope or behavioral detail without unnecessary wording.

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?

An output schema exists and the annotations cover safety traits, so the description need not explain return values or write hazards. However, with zero schema description coverage, the missing format/channels/directory parameter semantics are a clear completeness gap.

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

Parameters2/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 carry parameter meaning. It vaguely references track selections and destinations, but does not explain the format enum, channels, directory, or trackName semantics, leaving most parameter meaning undocumented.

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 states a specific verb and resource: exporting every positive-duration region in one label track as numbered audio files. It also clarifies that point labels are skipped, which distinguishes this from a generic export or label operation.

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

Usage Guidelines4/5

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

It provides clear usage context: one label track, positive-duration regions only, current mix, and explicit time/track selections. It does not name alternative tools or state explicit when-not conditions, so it falls short of full routing guidance.

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

Deploy Server