Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Set clip speed

clip_speed

Sets a clip's playback speed (ratio 0.25-4, 2.0 = double speed, half as long). The mode picks how: repitch (default, varispeed - pitch and length change together) or stretch (pitch-preserving time-stretch).

Instructions

Sets a clip's playback speed (ratio 0.25-4, 2.0 = double speed, half as long). The mode picks how: repitch (default, varispeed - pitch and length change together) or stretch (pitch-preserving time-stretch). Mode can also be changed on its own. lockTempo ties the clip to the project tempo (speed = project tempo / clip tempo, following tempo changes); the clip tempo is detected by beat tracking or given with tempo, which implies the lock.

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

Input Schema

NameRequiredDescriptionDefault
atNoTimeline position of the clip (in `unit`)
modeNoHow the speed is realised: varispeed or pitch-preserving
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)
ratioNoSpeed ratio (0.25-4)
tempoNoThe clip's own tempo in BPM; sets it and locks the clip
trackNoTrack id to narrow the match
lengthNoFit the clip to this timeline duration (in `unit`)
regionNoRegion name of the clip
projectYesPath to the .audium project package (absolute paths recommended)
lockTempoNoLock the clip to the project tempo (true) or release it (false)
semitonesNoPitch shift in semitones (ratio = 2^(n/12))

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

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

With no annotations, the description carries the behavioral burden and does well: it explains that speed changes affect pitch and length differently by mode, that ratio 2.0 makes the clip half as long, and that lockTempo follows project tempo changes. It does not explicitly discuss mutation side effects, reversibility, or failure behavior, though the task parameter schema covers undo grouping.

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 description is front-loaded with the core purpose and each sentence contributes useful semantics about ratio, mode, or tempo locking. It is dense and semicolon-heavy, which makes it slightly harder to scan than an ideal definition, but there is little wasted text.

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

Completeness5/5

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

Given 12 parameters with 100% schema description coverage, no annotations, and no output schema, the description supplies the behavioral context an agent most needs: ratio semantics, mode differences, and tempo-lock behavior. Remaining details such as targeting and undo grouping are handled well by the schema, so the definition is complete enough to call correctly.

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 real meaning beyond the schema for the core parameters: ratio behavior, default mode, repitch versus stretch, and the relationship between tempo, lockTempo, and detected clip tempo. It does not add much for targeting parameters such as at, track, region, or length, but those are already documented in the schema.

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 operation on a specific resource: setting a clip's playback speed, with ratio range and meaning. It also distinguishes the two realization modes, so an agent can distinguish this from adjacent clip tools such as clip_gain, clip_fades, or move_clip.

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?

It clearly explains the mode choice between repitch and stretch and when lockTempo or tempo should be used together. It does not explicitly compare this tool with sibling tools or state when not to use it, so it falls short of a full routing guide.

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