Skip to main content
Glama

edit_delete

Delete selected audio regions in Audacity without copying to clipboard. Use this tool to remove unwanted sections after selecting specific audio segments.

Instructions

Delete the selected audio (does not copy to clipboard). Select a region first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries full burden. Discloses that operation is destructive (deletes audio) and clipboard-independent. However, lacks mention of undoability, error behavior when no selection exists, or whether deletion is permanent versus recoverable—important gaps for a destructive operation.

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?

Two sentences with zero waste: first establishes operation and key behavioral trait (clipboard exclusion), second states prerequisite. Front-loaded with critical information, no redundancy.

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?

Adequate for a zero-parameter destructive operation with no output schema. Covers what is deleted, prerequisites, and differentiation from siblings. Missing only error-handling context and undo behavior, which would elevate it to completeness for a destructive 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?

Input schema contains zero parameters, warranting baseline score of 4. Description appropriately requires no parameter explanation since the tool operates solely on the current selection state.

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?

Specific verb 'Delete' + resource 'selected audio' with clear scope. Explicitly distinguishes from sibling tools like edit_cut by noting 'does not copy to clipboard', making the distinction between destructive deletion and clipboard-cutting immediately apparent.

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?

States prerequisite 'Select a region first', clearly indicating when the tool is ready for use. Implicitly guides against use when no selection exists. Could be strengthened by explicitly contrasting with edit_cut/edit_copy, but the clipboard note provides sufficient implicit guidance.

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