Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Delete unused regions

cleanup_regions

Deletes every region that has no clip on the timeline (the GUI's Delete Unused Regions). The audio files stay in the package.

Instructions

Deletes every region that has no clip on the timeline (the GUI's Delete Unused Regions). The audio files stay in the package.

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": {
      "project": "<project>"
    },
    "name": "cleanup_regions"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoName of the task this edit is part of, e.g. "remove speech pauses". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step
projectYesPath to the .audium project package (absolute paths recommended)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.7
    • addedInput schema / properties / task
      Added value: +{
      +  "description": "Name of the task this edit is part of, e.g. \"remove speech pauses\". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose the key destructive scope: all regions without clips are deleted while audio files remain. However, it does not state undo behavior, irreversibility, or confirmation expectations in the prose, leaving meaningful 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?

The description is two efficient sentences with the core operation front-loaded. The parenthetical GUI mapping and the audio-retention note both earn their place.

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?

For a simple destructive cleanup tool, the description covers what is removed and what is retained, and the schema covers the project path and undo grouping. It could say more about undo/irreversibility, but the essential call context is present.

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 100%, so both parameters are already documented in the schema, including the undo-step semantics of 'task'. The description adds no parameter-specific meaning beyond that baseline, so a 3 is appropriate.

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 a specific verb and resource: it deletes regions that have no clip on the timeline. It also distinguishes the operation from clip removal by clarifying that audio files stay in the package, so an agent can tell it apart from siblings like remove_clip.

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?

The condition for use is clear: clean up regions that contain no clips, equivalent to the GUI's 'Delete Unused Regions'. It does not explicitly name alternatives or when not to use it, but the scoping condition gives useful context without misleading exclusions.

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