Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Place clip

place_clip

Creates a new clip from an existing named region at a timeline position, on the track that owns the region (track only disambiguates same-named regions).

Instructions

Creates a new clip from an existing named region at a timeline position, on the track that owns the region (track only disambiguates same-named 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>",
      "region": "<region>",
      "at": "<at>"
    },
    "name": "place_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYesTimeline position for the new 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
unitNoUnit for positions (default bars; bars/beats are 1-based, seconds/clocks absolute)
trackNoTrack id, to disambiguate same-named regions
regionYesName of the region to place
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.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the non-obvious behavior that the clip lands on the track that owns the region, which is useful, but it says nothing about what is returned, whether the region is consumed or duplicated, or what happens on name collisions.

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?

A single front-loaded sentence with the operation first and the disambiguation caveat in a parenthetical. Nothing is wasted and nothing important is buried.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description should say more about effects and results - whether the originating region persists, what identifies the created clip, and any failure conditions. It is adequate on intent but thin on consequences.

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 coverage is 100%, so every parameter including at, unit, track, task, region and project is already documented in schema. The description only restates the track-disambiguation rule that the schema itself states, adding no syntax or format detail beyond it.

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 (creates) and resource (clip) and explains the source (existing named region) and placement (at a timeline position, on the region's owning track). It clearly differs from create_region or move_clip, though it does not name those siblings explicitly.

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 scenario is implied - you have a region and want a clip at a position - but there is no explicit when-not guidance or pointer to alternatives like move_clip, split, or create_region. The agent must infer the boundary.

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