Skip to main content
Glama

set_track_routing

Set a track's input, output, and monitoring in Ableton Live, leaving omitted settings untouched. Use it to route MIDI to instruments, record resampling, or send audio to returns and other tracks.

Instructions

Set a track's input/output routing and monitoring. Arguments left out are untouched. Names are matched against the options get_track_routing lists: exact (case-insensitive) first, else a unique substring.

Examples:

  • Layer one MIDI part on several instruments: on each extra MIDI track, input_type="", monitoring="in".

  • Record the main output (resampling): on an audio track, input_type="Resampling" (French Live: "Rééchantillonnage").

  • Send a track to a return or another track: output_type="".

Parameters:

  • track_index: Index of the track (return index for "return")

  • input_type / input_channel: Input routing ("MIDI From" / "Audio From")

  • output_type / output_channel: Output routing ("MIDI To" / "Audio To")

  • monitoring: "in", "auto" or "off"

  • track_type: "track" (default), "return" or "master" (output only)

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

Input Schema

NameRequiredDescriptionDefault
input_typeNo
monitoringNo
track_typeNotrack
output_typeNo
track_indexYes
input_channelNo
output_channelNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: 'Arguments left out are untouched' discloses partial-update semantics, and the exact-then-unique-substring matching rule explains how names resolve. Gaps remain on failure behavior (what happens with an ambiguous or unmatched name) and on permissions/undo, but the core mutation semantics are disclosed.

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 one-line purpose and the key 'untouched if omitted' rule, then examples, then parameters. The parameter block partly restates schema names but earns its place by adding routing semantics; the examples are compact and non-redundant.

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?

An output schema exists, so return values need not be explained, and the description supplies the routing vocabulary the bare schema lacks. It is nearly complete for a 7-parameter, required-track_index mutation tool; only error/ambiguity handling on name matching is unstated.

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?

Schema coverage is 0%, so the description must compensate, and it does for all seven parameters: track_index is qualified for returns, input_type/input_channel and output_type/output_channel are mapped to Live's 'MIDI From'/'Audio To' labels, and monitoring and track_type are given as closed value sets. The only weakness is that input_type vs input_channel (and output_type vs output_channel) are described jointly, leaving their distinction implicit.

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 and resource ('Set a track's input/output routing and monitoring') and immediately positions the tool against its read counterpart get_track_routing. An agent can distinguish it from sibling setters like set_track_send or set_track_arm 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?

Three concrete scenarios (MIDI layering, resampling, sending to a return/other track) tell the agent exactly when to reach for this tool, and it routes name discovery to get_track_routing. It stops short of stating when-not to use it or how it differs from set_track_send for return routing, which is the closest ambiguous sibling.

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

Deploy Server

Other Tools