Skip to main content
Glama
Ableton Producer MCP

Ableton Producer MCP

set_clip_automation

Write automation curves into one clip's envelope to control device or mixer parameters over time, replacing existing data when needed.

Instructions

Write an automation curve into one clip's envelope.

points: [{"time": beats, "value": v, "step": false}, ...] with times in clip-local beats (0 = clip start, same timeline as note start_time). Between points the value ramps linearly; "step": true holds the point's value until the next point (a jump). Before the first / after the last point the end values are held, so one point writes a flat line. Ramps are written as steps resolution beats wide.

Parameters:

  • track_index, clip_index, clip_view: which clip (see get_clip_automation)

  • points: The curve (see above)

  • resolution: Step width for ramps in beats (default 1/32 note = 0.125)

  • clear_existing: Replace the parameter's existing envelope in this clip (default True)

  • 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>",
      "clip_index": "<clip_index>",
      "points": "<points>"
    },
    "name": "set_clip_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
clip_viewNosession
clip_indexYes
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.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses that clear_existing defaults to True and replaces the parameter's existing envelope (a destructive side effect), that values are clamped to the parameter's min..max, that ramps are quantized into resolution-wide steps, and that end values are held outside the point range. It omits failure modes (nonexistent clip/parameter, view mismatch) and permission or undo behavior.

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 the core action, then a labeled 'Parameters' list and a 'Target' section, which is easy to scan. Slightly long for a single tool, but nearly every line adds semantics the 0%-coverage schema lacks, so little is wasted.

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?

With an output schema present, return values need not be described, and all 12 parameters plus curve interpolation behavior are covered. What remains unstated is preconditions and error behavior (clip_view 'session' vs 'arrangement' validity, missing device/parameter handling) for a 12-parameter mutation tool.

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 description coverage is 0% and the points array is an untyped object bag, so the description is doing all the work: it defines the point object keys (time, value, step), the beat timeline origin, ramp vs step semantics, and units for values. It also explains resolution, clear_existing, user_prompt, target_type, device_index/parameter_index, mixer_name, and send_index, leaving essentially no parameter ambiguous.

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?

States a concrete verb and resource: 'Write an automation curve into one clip's envelope', and the 'one clip' scoping separates it from set_arrangement_automation and clear_clip_automation in the sibling list. The target block further narrows it to device or mixer parameters, so an agent knows exactly what object is mutated.

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 actionable routing guidance: 'see get_clip_automation' for clip identification and 'discover them with get_device_parameters' for device/parameter indices, plus which target_type/mixer_name combinations are legal. It does not contrast itself with the static-value sibling set_device_parameter or state when to prefer arranging over session clips, so a small inference gap remains.

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