Skip to main content
Glama

label_delete_audio_at

Delete audio under one labeled region by its index, then close the gap and remove the leftover label marker.

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
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and excels: it discloses that this is a composite orchestration of multiple Audacity commands, explains the default gap-closing behavior and close_gap=False alternative, states that all tracks are selected so label tracks ripple, and reveals that deleting audio does not remove the label and that the leftover marker is cleared by default. These are non-obvious side effects an agent needs to know.

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 long but structured into focused paragraphs and a clear Args list. Every major sentence adds essential context—scope, sibling differentiation, composite nature, side effects, and parameter behavior. It could be slightly trimmed without losing value, but the length is largely justified for a complex operation.

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 composite mutation tool with no annotations and no output schema, the description covers everything needed to call it correctly: operation semantics, index-based targeting, default and opt-out behaviors, label track alignment, leftover marker handling, and clear alternatives. No critical operational detail is missing.

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?

Schema coverage is 0%, but the Args section fully compensates: index is defined as 'Flat label index from label_list', close_gap explains the exact timeline effect and default True, and delete_label explains that it removes the leftover marker and default True. This adds meaning far beyond the bare schema types and defaults.

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 first sentence states a specific verb and resource: 'Delete the audio under ONE label, picked by index'. It immediately distinguishes itself from sibling tools label_delete (marker only) and label_delete_regions (every label in current selection, no index), so an agent can tell exactly what it does and how it differs.

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 explicitly names when to use this tool vs alternatives: 'not label_delete (marker only) or label_delete_regions (every label in the current selection, no index)' and later 'Use label_delete instead to remove a label without touching any audio.' It also clarifies how composite label region tools differ, so the agent has clear routing guidance.

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

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

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