Skip to main content
Glama

label_delete

Delete a label by index from label_list without touching audio. Selects the label's span on its label track and split-deletes it, preserving audio and re-adding any fully contained labels.

Instructions

Delete a single label without touching the audio.

Get the index from label_list. Audacity has no scripting command for deleting one label, so this selects the label's own span on its own label track and split-deletes it — audio tracks are never in the selection, and nothing downstream shifts in time.

Other labels on the same track that sit entirely inside the deleted label's span would be removed as collateral, so they are re-added afterwards. A label that only partially overlaps the span may be trimmed to the boundary; check label_list afterwards if labels on that track overlap each other.

To delete a label and the audio under it, use label_delete_audio_at.

Args: index: Flat label index from label_list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes
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 full disclosure duty, and it delivers: it reveals the workaround implementation (selecting the label span and split-deleting), guarantees audio tracks are never selected and nothing shifts in time, and discloses collateral deletion/trimming of overlapping labels. This goes well beyond a typical mutation description.

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 main action is front-loaded, and each subsequent paragraph covers a necessary behavioral consequence or alternative. Despite its length, every sentence adds information the agent needs to call it safely.

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 destructive label operation with one parameter, no annotations, and no output schema, the description covers what happens, when it differs from the sibling, and how to verify results via label_list. No critical operational gap remains.

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% and the schema only gives type/title, so the description's Args line is essential. 'Flat label index from label_list' clarifies where the index comes from and what kind of index it is, adding real meaning beyond the schema; it just stops short of specifying bounds or 0-based indexing.

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?

Opens with 'Delete a single label without touching the audio' — a specific verb, resource, and a key constraint that immediately separates it from label_delete_audio_at. The title/name alone would not convey the no-audio scope, but the description does.

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?

Explicitly instructs the agent to get the index from label_list and names the sibling label_delete_audio_at for the case where audio should also be deleted. It also warns about overlapping-label collisions and tells the agent to check label_list afterward, which is direct operational 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