Skip to main content
Glama
Ableton Producer MCP

Ableton Producer MCP

set_arrangement_automation

Draw parameter curves as real Arrangement automation in Ableton Live. Specify points in beats to create filter sweeps, builds, and fades across a track's timeline.

Instructions

Automate a parameter across the Arrangement timeline (filter sweeps, builds, fades).

points: [{"time": beats, "value": v, "step": false}, ...] with times in absolute Arrangement beats (0 = bar 1; bar N starts at (N-1)*4 in 4/4). Between points the value ramps linearly; "step": true makes a jump.

Writes real track automation. Live's API can't create envelopes in Arrangement clips, so every MIDI clip on the track overlapping the span from the first to the last point is rebuilt through an empty Session slot (same notes, name, color, plus the curve) and duplicated back onto itself; Live turns the envelope into track automation over that clip's span. Inside a rebuilt clip the curve holds its end values outside the span; the lane outside rebuilt clips is left untouched, so cover every clip where the value should differ from the parameter's current one.

Limits: the track needs one empty Session slot and MIDI clips covering the span. Audio clips, and clips looped or trimmed inside the Arrangement, are skipped and listed under "skipped". Group tracks and audio tracks monitoring an input can't be automated through the API.

Parameters:

  • track_index: Track to automate

  • points: The curve (see above)

  • resolution: Step width for ramps in beats (default 0.125)

  • clear_existing: Kept for compatibility; the lane is always replaced over each rebuilt clip

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

Target (what to automate):

  • target_type: "device" (a device parameter) or "mixer" (track mixer)

  • device_index, parameter_index: for "device"; discover them with get_device_parameters

  • mixer_name: for "mixer": "volume", "panning" or "send"

  • send_index: for mixer_name "send" Values are in the parameter's own units (the same min..max that get_device_parameters reports), and are clamped to that range.

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>",
      "points": "<points>"
    },
    "name": "set_arrangement_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
mixer_nameNovolume
resolutionNo
send_indexNo
target_typeNodevice
track_indexYes
user_promptNo
device_indexNo
clear_existingNo
parameter_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5+automation.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: it discloses the destructive implementation (MIDI clips are rebuilt through an empty Session slot and duplicated back onto themselves), the exact skip conditions (audio clips, looped/trimmed clips, group tracks, monitored audio tracks), the 'skipped' reporting, and value clamping. It even flags that clear_existing is effectively a no-op because the lane is always replaced.

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?

Front-loaded with purpose, then clearly sectioned into curve format, behavior, limits, parameters, and target. Dense but nearly all of it earns its place; minor redundancy in repeating the points reference and the parameter list that partially restates the header block.

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?

For a complex 10-parameter mutation tool, the description covers preconditions, side effects, failure/skip modes, and a pointer for discovering device indices; an output schema exists and the 'skipped' return is already acknowledged, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description compensates for essentially every one of the 10 parameters: the points object shape and beat semantics, linear ramps vs step jumps, resolution, target_type, device_index/parameter_index with a discovery pointer to get_device_parameters, and the mixer_name/send_index pairing with allowed values.

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?

Opens with a specific verb and resource ("Automate a parameter across the Arrangement timeline") plus concrete use cases (filter sweeps, builds, fades). The Arrangement scope cleanly separates it from the clip-automation siblings (set_clip_automation, get_clip_automation, clear_arrangement_automation).

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 strong operational preconditions: the track needs an empty Session slot and MIDI clips covering the span, and the user must 'cover every clip where the value should differ from the parameter's current one.' It does not explicitly name an alternative tool (e.g. set_device_parameter for static values, set_clip_automation for clip lanes), so routing is inferable rather than stated.

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