Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Labels Set

audacity_labels_set

Destructive

Add point/region labels to a named track, creating it if needed and keeping existing labels for chapters, picture events, or script lines. Disable the label naming dialog first.

Instructions

Add point or region labels to a named label track, creating it if needed and retaining existing labels. Use them for chapters, picture events or script lines. Disable the label naming dialog in Preferences > Tracks > Track Behaviors before adding labels.

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": {
      "labels": "<labels>"
    },
    "name": "audacity_labels_set"
  }
}

Input Schema

Name	Required	Description	Default
`labels`	Yes
`trackName`	No		Labels

Output Schema

Name	Required	Description	Default
`labels`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations it discloses that a missing track is created implicitly and that existing labels are retained, plus the dialog-setting prerequisite that would otherwise silently block a call. There is mild tension with destructiveHint=true, since an agent may read 'retaining existing labels' as non-destructive; the description does not state what happens on overlapping/duplicate labels or whether the edit is undoable.

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 tight sentences, front-loaded with the action and its side effects. The use-case sentence ('chapters, picture events or script lines') is the least essential but still cheap and aids selection.

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?

An output schema covers return values and annotations cover the safety profile, so the description's remaining job is mutation behavior and prerequisites — both addressed. Gaps are minor: conflict/overwrite behavior for existing labels and idempotency expectations are unstated despite idempotentHint=false.

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 carry the load. It does explain the key semantic — that a label can be a point or a region (i.e. start-only vs start+end) and that the track is referenced by name — but it never covers the trackName default of 'Labels', the 1-500 label count limit, the 0-86400 range/units, or the text length cap.

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 names a specific verb and resource ('Add point or region labels to a named label track') and clarifies scope ('creating it if needed and retaining existing labels'). That is enough to separate it from audacity_labels (read) and audacity_labels_file (file import) without opening schemas, though no sibling is named explicitly.

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 gives concrete use cases ('chapters, picture events or script lines') and a hard operational prerequisite: disable the label naming dialog in Preferences > Tracks > Track Behaviors. It does not say when NOT to use it or point at audacity_labels_file / audacity_labels as alternatives, so it stops 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