Skip to main content
Glama

live12_audio_clip_set_warp

Configure an Ableton Live audio clip's warping mode, pitch shift, and gain to control time-stretching, tuning, and level within the MCP workflow.

Instructions

Configures audio clip warping mode, pitch shift, and gain in Ableton Live 12.

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": {
      "track_index": "<track_index>",
      "slot_index": "<slot_index>"
    },
    "name": "live12_audio_clip_set_warp"
  }
}

Input Schema

NameRequiredDescriptionDefault
gainNoAudio clip gain factor or dB value.
warpingNoEnable or disable audio time-stretching / warping.
warp_modeNoWarping algorithm.
slot_indexYesZero-based clip slot index.
pitch_shiftNoCoarse pitch shift in semitones [-48.0..48.0].
track_indexYesZero-based track index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about what happens if the target slot is empty or holds a MIDI clip, whether warp_mode is ignored when warping is false, whether changes are undoable, or what the response contains. For a mutation tool with zero annotation coverage this is a substantial gap.

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?

A single front-loaded sentence with no filler, sized appropriately for a simple setter. It is close to optimally concise, though the brevity comes at the cost of the behavioral detail noted elsewhere.

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?

A six-parameter mutation tool with no annotations and no output schema needs more than one sentence: error conditions, the warping/warp_mode dependency, and target-clip validity are all undocumented. The description is not wrong, just insufficient for the tool's complexity.

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% and the enum for warp_mode plus ranges for pitch_shift are already documented in the schema, so the baseline is 3. The description only echoes three of the six parameters (warping, pitch shift, gain) and adds no clarification of the ambiguous 'gain factor or dB value' semantics.

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 ('Configures') and resource ('audio clip warping mode, pitch shift, and gain') in a named host (Ableton Live 12), so the agent knows exactly which clip properties are touched. It doesn't explicitly differentiate itself from nearby siblings like live12_clip_set_properties or live12_audio_clip_add_warp_marker, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to prefer this over live12_clip_set_properties, nor any stated preconditions (clip must exist, must be an audio clip, warping likely must be enabled before warp_mode takes effect). Usage is implied only by the listed properties.

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

Deploy Server

Other Tools