Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Auto-edit clip

auto_edit

Segments a clip on a track using cached analysis results (run analyze first). Splits the clip into musically-aligned regions.

Instructions

Segments a clip on a track using cached analysis results (run analyze first). Splits the clip into musically-aligned regions.

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

Input Schema

NameRequiredDescriptionDefault
clipNoPlaylist item id (default: the track's clip)
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
trackNoTrack id (default 0; imported audio lands on a new track)
projectYesPath to the .audium project package (absolute paths recommended)
measuresNoSegment length in measures
segmentsNoNumber of segments
crossfadesNoApply crossfades at joints (default true)
duration_secondsNoTarget duration

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

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden and mostly doesn't. It never says whether the original clip is consumed or retained, whether existing regions are replaced, what side effects occur on the track, or what is returned; the only behavioral hint (undo grouping) lives in the schema's task parameter, not the 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?

Two short sentences, prerequisite front-loaded and result described second. Nothing is wasted and the essential dependency appears before the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter mutation tool with no annotations and no output schema, the description is thin. It omits what is returned (region ids?), whether segments/measures/duration_seconds are mutually exclusive targeting options, and what happens to the source clip — all things an agent must know to call it correctly.

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 all eight parameters are already documented, and the description adds no param-level meaning. Baseline 3 applies; the description does not clarify the relationship between segments, measures, and duration_seconds, which is the one ambiguity the schema leaves open.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — segments/splits a clip on a track into musically-aligned regions — which is concrete and distinct from generic operations. It partially distinguishes itself from siblings by tying itself to analyze output, but never contrasts with splitor create_region, which produce superficially similar results.

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?

"run analyze first" is a genuine prerequisite and the strongest usage signal in the description. However, there is no guidance on when to choose auto_edit over the sibling split or create_region, and no statement of when this tool should not be used.

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