ableton-mcp

Overview Schema Source Related Servers Discussions Admin

set_track_mix

Update a track's mixer settings—volume, pan, sends, mute, or solo—in Ableton Live by sending only the parameters you want to change. Returns the resulting mix.

Instructions

Set a track's mixer; give only what you want to change. volume_db in dB (0 is Live's default, max +6). pan -50..50 (-50 = 50L, 50 = 50R). sends maps a return letter to dB, e.g. {"A": -12}. To silence a track use mute. solo is not exclusive: Live does not unsolo other tracks, so unsolo them yourself. Returns the track's resulting mix.

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": "<track>"
    },
    "name": "set_track_mix"
  }
}

Input Schema

Name	Required	Description	Default
`pan`	No
`mute`	No
`solo`	No
`sends`	No
`track`	Yes
`volume_db`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Nov 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds real behavioral context on top: partial updates leave other fields untouched, solo does not auto-unsolo other tracks (a non-obvious side-effect an agent would otherwise get wrong), and the call returns the resulting mix. Reversibility/undo is not mentioned, so not a 5.

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

Conciseness5/5

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

Four dense sentences, each front-loading the contract then a specific constraint (dB range, pan mapping, sends example, solo caveat). No filler and no repetition of the schema structure.

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?

Covers the mutation semantics, unit conventions, the non-exclusive solo gotcha, and states the return value, which compensates for the absence of an output schema. The main remaining gap is how 'track' is identified, which matters since it is the sole required parameter.

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%, so the description carries the full burden and does so well: volume_db units, 0 default and +6 max; pan range -50..50 with the -50=50L / 50=50R mapping; sends as a return-letter-to-dB map with a concrete example. It also explains the mute/solo semantics. Only the required 'track' parameter's expected identifier form (index vs name) is left unstated.

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 specific verb and resource ('Set a track's mixer') plus the partial-update contract ('give only what you want to change'). The 'mixer' framing separates it from siblings like set_device_parameters (device params) and set_tempo (global tempo) without needing to name them.

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 clear when-to-use guidance: only pass the fields you intend to change, and 'to silence a track use mute' steers the agent away from abusing volume_db for muting. It also warns that solo is not exclusive and the caller must unsolo other tracks. It does not name alternative tools or state when-not to use this one.

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