Skip to main content
Glama

update_track

Change only the specified properties of an Ableton Live track—such as name, volume, pan, sends, mute, solo, arm, or routing—with per-field feedback and a single undo step.

Instructions

Change a track's name, color, volume, pan (or split-stereo pans), sends, mute, solo, arm, monitoring, crossfader assignment, group folding or routing (input and output, with channels). On the master it also sets the cue volume and crossfader.

Only the fields you give change, each with its own result line ("now" shows what Live displays afterwards; a field that fails says why and the others still apply). Works for return tracks (rA) and the master (m). One undo step.

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": "update_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
armNoRecord arm: true / false. Empty: unchanged.
panNoPan as Live shows it: "C", "25L", "30R" (or -50..50).
muteNotrue / false. Empty: unchanged.
nameNoNew name.
soloNotrue / false. Empty: unchanged.
inputNoInput routing by the name Live shows, e.g. All Ins.
sendsNoSend levels. Example: [{"return": "A", "db": "-12"}]
trackYesTrack address: t0 for the first track (numbers from 0), rA for return track A, m for the master. Example: t2
foldedNoGroup track: true folds it, false opens it.
outputNoOutput routing by the name Live shows, e.g. Master.
pan_leftNoSplit stereo: left pan, like pan (e.g. 25L).
crossfadeNoCrossfader assignment: A, None or B.
pan_rightNoSplit stereo: right pan, like pan (e.g. 30R).
volume_dbNoVolume in dB: "-6", "0", "-inf". Empty: unchanged.
crossfaderNoMaster only: crossfader position -1 (A) to 1 (B).
monitoringNoMonitoring: In, Auto or Off.
color_indexNoLive's color number. Empty: unchanged.
implicit_armNoImplicit arm (Push-style arm): true / false.
panning_modeNostereo or stereo_split.
cue_volume_dbNoMaster only: the cue/preview volume in dB.
input_channelNoInput channel by the name Live shows, e.g. 1/2.
output_channelNoOutput channel by the name Live shows, e.g. 1/2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent), and the description adds real behavioral substance on top: per-field result lines showing what Live displays afterwards, per-field failure isolation ('a field that fails says why and the others still apply'), and a single undo step for the whole call. Those details about error handling and reversibility are exactly what an agent needs and cannot get from the annotations.

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?

Two compact paragraphs, front-loaded with the capability and followed by the mutation semantics and undo behavior. The long field enumeration in the first sentence partly duplicates the schema and could be trimmed, but the rest earns its space.

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 22-parameter single-required-parameter mutation tool with no output schema, the description covers targeting scope, partial-update semantics, per-field error reporting, and undo granularity. The only real gap is that the shape of the success 'result line' is described in prose rather than precisely, but nothing essential to correct invocation is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents each of the 22 parameters, including the 'Empty: unchanged' convention and the t0/rA/m addressing. The description restates field families and the empty-means-unchanged rule rather than adding syntax or format meaning beyond the schema, which is the baseline case for full coverage.

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 ('Change a track's name, color, volume, pan...') and enumerates the mutable field families, so the agent can tell it apart from create_track, read_track, and update_device at a glance. It also states the target scope (regular tracks, return tracks rA, master m), which no sibling name alone conveys.

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?

'Only the fields you give change' defines the partial-update usage pattern explicitly, and 'Works for return tracks (rA) and the master (m)' plus 'On the master it also sets the cue volume and crossfader' tells the agent which targets are legal for this tool. It stops short of naming when to prefer read_track or update_device instead, so there is no explicit alternative routing, but the usage context is clear.

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