Skip to main content
Glama

label_delete_audio_at

Deletes the audio under a single selected label by index, with options to close the gap and remove the leftover label marker. Keeps the timeline compact and all track positions aligned after removal.

Instructions

Delete the audio under ONE label, picked by index — not label_delete (marker only) or label_delete_regions (every label in the current selection, no index).

This is a custom, composite operation built for podcast/transcript-based editing, not a 1:1 wrapper over a single Audacity scripting command — unlike label_cut_regions/label_delete_regions/label_silence_regions/ label_split_regions/label_join_regions, which each call exactly one Audacity command. Audacity has no "delete this one labeled take" command, so this orchestrates several: SelAllTracks, then SelectTime, then Delete/SplitDelete, then clears the leftover marker.

By default the gap closes and everything after shifts left, exactly as label_delete_regions does. Pass close_gap=False to leave silence of the same length instead, keeping the timeline length and everything after it in place.

All tracks are selected first, so label tracks ripple along with the audio and later labels stay aligned with it.

Deleting the audio does NOT remove the label — it collapses to a zero-length marker sitting where the audio used to be. This tool clears that leftover marker too, matching what clicking a label and pressing Delete does in Audacity: the audio and the label both go. Pass delete_label=False to keep it as a marker of where the cut was made. Use label_delete instead to remove a label without touching any audio.

Args: index: Flat label index from label_list close_gap: Close the gap and shift later audio left. Default: True delete_label: Also remove the label left behind. Default: True

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes
close_gapNo
delete_labelNo
Behavior5/5

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

No annotations are provided, so the description carries the full burden — and it delivers thoroughly. It discloses the multi-command orchestration (SelAllTracks, SelectTime, Delete/SplitDelete, marker clear), that all tracks are selected first so label tracks ripple, that the leftover marker is cleared matching Audacity's Delete-on-label behavior, and the default gap-closing behavior vs. close_gap=False leaving silence. This is complete behavioral disclosure for a mutation tool.

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 thorough but somewhat lengthy, running about 250+ words. The opening sentence front-loads the core purpose and sibling distinction, and the Args section is well-organized. However, some redundancy exists between the prose explanation of close_gap and delete_label and the Args list, which repeats the same information. Slightly tighter could earn a 5.

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

Completeness5/5

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

For a 3-parameter composite mutation tool with no annotations and no output schema, this description is remarkably complete. It explains the underlying mechanism, the behavioral toggles, the side effects on label tracks and markers, and the relationship to sibling tools. Given the complexity of the operation (orchestrating multiple Audacity commands), the description fully equips an agent to use and understand this tool.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate and largely does. index is explained as a flat label index from label_list; close_gap's effect on timeline length and shifting is described; delete_label's effect on the leftover marker is described. However, index's semantics could be slightly more explicit about whether it's zero-based, though the reference to label_list helps. Overall strong compensation for complete schema absence.

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 exactly what the tool does: deletes audio under ONE label picked by index, and explicitly distinguishes it from label_delete (marker only) and label_delete_regions (every label, no index). It uses a specific verb+resource combination and differentiates from the two closest siblings with concrete differences.

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?

The description is exemplary here. It explains this is a composite operation vs. the other label_*_regions tools that wrap single Audacity commands, gives explicit when-to-use guidance (podcast/transcript editing), and even names label_delete as the alternative to remove a label without touching audio. It also clarifies the close_gap and delete_label behavioral toggles with precise consequences.

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