Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Move clip

move_clip

Moves one clip to a new timeline position and/or onto another track. Address it by position (at) or region name; the address must match exactly one clip.

Instructions

Moves one clip to a new timeline position and/or onto another track. Address it by position (at) or region name; the address must match exactly one clip. to_track takes a track id, or "new" to create a track for it; without to the clip keeps its position. Give at least one of to and to_track.

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

Input Schema

NameRequiredDescriptionDefault
atNoCurrent position of the clip (exclusive with region)
toNoTarget timeline position (default: unchanged)
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 of the clip
projectYesPath to the .audium project package (absolute paths recommended)
to_trackNoTarget track id, or "new" to create a track

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.1/5.0
Behavior4/5

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

With zero annotations the description carries the full burden, and it does disclose meaningful behavior: the exact-one-match addressing rule (an ambiguity/error condition) and the side effect that to_track="new" creates a track. It leaves out what happens when the target track/position is occupied and says nothing about the response.

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?

Four short sentences, front-loaded with the action, then addressing rules, then target rules, then the minimum-argument constraint. No filler and nothing buried.

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 an annotation-free mutation tool with no output schema, it covers the essentials: addressing, mutual exclusivity, the track-creation side effect, and the required minimum arguments. Occupied-target behavior and confirmation of the resulting clip state are the remaining gaps.

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, but the description adds value beyond the schema by tying at/region together as a single mutually exclusive 'address' that must be unique, and by restating the to_track="new" and unchanged-position defaults in one coherent model.

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 precise verb+resource+scope: moves exactly one existing clip either in time, to another track, or both. That clearly separates it from remove_clip, but it never mentions place_clip, which is the sibling an agent could most plausibly confuse with this one.

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?

Gives concrete preconditions for use: address by position (at) or region name, the address must resolve to exactly one clip, and at least one of to/to_track must be supplied. It stops short of naming when a different tool (e.g. place_clip) is the right choice.

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