Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Edit

audacity_edit

Destructive

Edit audio tracks by splitting, trimming, duplicating, deleting, cutting, copying, silencing, joining, or disjoining explicit time ranges.

Instructions

Split, split-new, trim, duplicate, delete, cut/copy, silence or join/disjoin audio on explicit tracks and time range. split accepts a cursor; delete closes the gap while split_delete retains timing. Paste is not offered: it depends on the system clipboard.

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": {
      "action": "<action>",
      "track": "<track>"
    },
    "name": "audacity_edit"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No
`start`	No
`track`	Yes
`action`	Yes
`trackCount`	No

Output Schema

Name	Required	Description	Default
`end`	Yes
`reply`	Yes
`start`	Yes
`track`	Yes
`action`	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?

The annotations already declare destructive=true and readOnly=false, and the description adds meaningful behavior: delete closes gaps, split_delete preserves timing, and paste is unavailable because it depends on the system clipboard. It still does not mention undo behavior, selection requirements, or other side effects of mutating audio.

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 two dense sentences with the action list front-loaded and no wasted wording. The second sentence adds useful distinctions and the paste exclusion without digressing.

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, so return values need not be explained. However, for a destructive tool with twelve actions and five parameters at 0% schema description coverage, the definition leaves important gaps around trackCount and start/end semantics.

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 for five undocumented parameters. It clarifies the action choices somewhat, including the split cursor and the delete versus split_delete distinction, but it does not explain start/end units, track identifier semantics, or trackCount.

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 specific audio-editing verbs (split, trim, duplicate, delete, cut/copy, silence, join/disjoin) and the resource and scope: explicit tracks and a time range. It is clearly an editing tool, though it does not explicitly distinguish itself from sibling tools like audacity_track_edit or audacity_clip_set.

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 actionable distinctions among actions, notably that split accepts a cursor and that delete closes the gap while split_delete retains timing. It also explains why paste is excluded, but it does not state broader conditions such as when to use this tool versus other editing tools.

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

Deploy Server