Skip to main content
Glama
Ableton Producer MCP

Ableton Producer MCP

clear_clip_automation

Remove automation envelopes from a clip, targeting one parameter or clearing every envelope when all_parameters is enabled.

Instructions

Remove automation from one clip: a single parameter's envelope, or every envelope when all_parameters is True.

Parameters:

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

  • all_parameters: Clear every envelope in the clip instead of one target

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

Input Schema

NameRequiredDescriptionDefault
clip_viewNosession
clip_indexYes
mixer_nameNovolume
send_indexNo
target_typeNodevice
track_indexYes
user_promptNo
device_indexNo
all_parametersNo
parameter_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5+automation.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. It says 'Remove' but never discloses whether clearing is destructive, undoable, or what happens to a device-targeted envelope if the device is later removed. Worse, the closing sentence about values 'clamped to that range' is a leftover from the set_clip_automation tool and describes behavior this tool cannot exhibit, since it accepts no values at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded summary followed by two labeled bullet groups is well organized and easy to scan, and the parameter groupings mirror the actual call flow. However, the final two lines about value units and clamping are wasted text that actively misleads, and the 'Target (what to automate)' heading is stale wording for a clearing operation.

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

Completeness3/5

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

Return values need not be explained because an output schema exists, and all ten parameters receive at least a one-line gloss. But for an unannotated mutation tool the description should state reversibility and the practical difference between session and arrangement clip views, which it defers entirely to get_clip_automation. The incorrect clamping sentence further undercuts completeness.

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?

With 0% schema description coverage across 10 parameters, the description does real work: it groups them into clip selectors, an all_parameters switch, a telemetry field, and target selectors. It supplies enum-like values the schema lacks ('device' or 'mixer'; 'volume', 'panning', 'send') and explains that send_index only applies when mixer_name is 'send'. The one misstep is the trailing units/clamping sentence, which has no bearing on any parameter here.

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 opening sentence names a specific verb ('Remove') and resource ('automation from one clip') and states both operating modes: a single parameter's envelope, or every envelope when all_parameters is True. The phrase 'one clip' plus the clip_view parameter implicitly separates it from clear_arrangement_automation and clear_notes_from_clip, so an agent can route correctly without opening the schema.

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 routes the agent to siblings for prerequisite discovery ('see get_clip_automation' for clip identification, 'discover them with get_device_parameters' for device/parameter indices), which is genuine when-to-use guidance. It never states when NOT to use it (e.g. versus clear_arrangement_automation for arrangement automation, or set_clip_automation for overwriting), so it stops short of full alternative routing.

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