Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Split clips

split

Splits the clip under the given timeline position into two on every track that has one there (the GUI's Split command). Fails with nothing_to_split when no clip spans the position.

Instructions

Splits the clip under the given timeline position into two on every track that has one there (the GUI's Split command). Fails with nothing_to_split when no clip spans the position.

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>",
      "at": "<at>"
    },
    "name": "split"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesTimeline position to split at, e.g. 23 for bar 23
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)
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

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the split applies across every track with a clip at the position and that it fails with nothing_to_split when no clip spans the position, but it does not state whether the edit is undoable, what permissions are required, or what side effects occur on clip selection or automation.

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 tightly written sentences with the core operation front-loaded, followed by the multi-track scope and failure condition. The parenthetical GUI command reference earns its place by anchoring the operation for users familiar with the app.

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 relatively simple edit tool with two required parameters and a fully described schema, the description gives enough to invoke it correctly: what it does, its scope across tracks, and its failure behavior. It stops short of covering mutation safety or undo semantics, though the schema's `task` description partly addresses undo grouping.

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 the baseline is 3. The description reinforces that `at` is a timeline position and that splitting applies across tracks with a clip, but it does not add format or syntax details beyond the schema and says nothing about `project`, `task`, or `unit`.

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 splits the clip under the given timeline position into two. It also clarifies the non-obvious scope — every track that has a clip at that position — and identifies it as the GUI's Split command, which distinguishes it from sibling edit tools like move_clip or 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 Guidelines3/5

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

Usage is implied by the operation itself and by the parenthetical reference to the GUI's Split command, but there is no explicit when-to-use or when-not-to-use guidance relative to alternatives. The failure condition 'nothing_to_split when no clip spans the position' is a useful constraint, though it is not a routing guideline between sibling tools.

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