Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Remove clips

remove_clip

Removes the clip at a timeline position (one clip; ambiguity across tracks needs track), or every placement of a named region. delete_region also drops the region itself unless other clips use it.

Instructions

Removes the clip at a timeline position (one clip; ambiguity across tracks needs track), or every placement of a named region. delete_region also drops the region itself unless other clips use it.

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": "remove_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoTimeline position of the clip (exclusive with region)
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
unitNoUnit for positions (default bars; bars/beats are 1-based, seconds/clocks absolute)
trackNoTrack id
regionNoRegion name; removes every placement
projectYesPath to the .audium project package (absolute paths recommended)
delete_regionNoAlso delete the region from the pool

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

A3.9/5.0
Behavior3/5

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

With no annotations, the description does add useful behavioral context: it removes either one clip or all placements of a region, and delete_region drops the region itself unless other clips use it. However, it does not state whether removal is destructive or reversible, what permissions are needed, or what happens when no matching clip is found.

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 definition is two dense sentences, front-loaded with the core action and followed by the region-deletion caveat. It is efficient, though the phrase 'ambiguity across tracks needs track' is telegraphic and could be clearer.

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?

The schema fully documents seven parameters, so the description does not need to explain project, unit, or task. It covers the tricky mode selection and conditional region deletion well, but for a mutation tool with no annotations it could say more about irreversibility or the undo grouping behavior.

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 100%, so the baseline is 3; however, the description adds cross-parameter meaning beyond the schema. It explains that track resolves ambiguity across tracks, that region removes every placement, and that delete_region also drops the region unless other clips still use it.

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 removes a clip at a timeline position or every placement of a named region. It clearly defines the two operating modes and the single-clip versus all-placements scope, so an agent can distinguish this from move_clip or place_clip.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies mode selection: use a timeline position for one clip, or a region name to remove every placement. It also notes that ambiguity across tracks requires the track parameter, but it does not name alternatives such as cleanup_regions or explain when not to use this tool.

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