Skip to main content
Glama
Ableton Producer MCP

Ableton Producer MCP

clear_arrangement_automation

Flattens a parameter's Arrangement automation to a constant value across a specified beat range, overwriting the span covered by MIDI clips to fix automated changes.

Instructions

Flatten a parameter's Arrangement automation to a constant value over [start_time, end_time) in beats (end_time < 0 means to the last Arrangement clip).

Live's API can't delete track automation, so the span covered by the MIDI clips in range is overwritten with value (same mechanism and limits as set_arrangement_automation). To remove a lane completely, delete it in Live.

Parameters:

  • track_index: Track to flatten

  • value: The constant to write (parameter units, e.g. its un-automated setting)

  • start_time, end_time: Arrangement beat range

  • 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>",
      "value": "<value>"
    },
    "name": "clear_arrangement_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
end_timeNo
mixer_nameNovolume
send_indexNo
start_timeNo
target_typeNodevice
track_indexYes
user_promptNo
device_indexNo
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?

With no annotations, the description carries the burden well: it discloses the surprising behavior behind the 'clear' name (the span is overwritten, not deleted), states the API limitation that track automation can't be deleted, defines the affected span as whatever the MIDI clips in range cover, and notes values are clamped to the parameter's min..max. It loses a point for deferring the actual limits to 'same mechanism and limits as set_arrangement_automation' rather than stating them, and for saying nothing about reversibility/undo.

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 behavior, then organized into a caveats paragraph and a labeled 'Target (what to automate)' block that reads well. It is somewhat long and repeats the unit/clamping idea in two places, but no sentence is truly dead weight.

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?

For a 10-parameter mutation tool with no annotations, the description covers effect, scope, limits, target selection, and units, and an output schema exists so return values need not be explained. The only real gap is the outsourced limit details via cross-reference to set_arrangement_automation.

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 10 parameters are documented in prose, including the conditional grouping of target_type/device_index/parameter_index vs mixer_name/send_index, valid mixer_name values, the units of value, the default-implied semantics of end_time, and even the telemetry purpose of user_prompt. This more than compensates for the empty schema descriptions.

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 first sentence states a concrete verb (flatten to a constant value), the exact resource (a parameter's Arrangement automation), and the span semantics in beats with the end_time < 0 convention. It also implicitly separates the tool from set_arrangement_automation and clear_clip_automation by explaining that this is overwrite-based rather than a true delete.

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 frames the situation where this tool is the answer (flattening a range to a constant) and explicitly redirects the truly-removal case: 'To remove a lane completely, delete it in Live.' What's missing is explicit routing against the closely named siblings set_arrangement_automation and clear_clip_automation, so the agent must infer the choice.

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