ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_track_midi_routing

Read-onlyIdempotent

Reads a track's native MIDI note routing (input/output notes and scale transposition) from its MIDIMap. Reports unsupported when Live does not expose it.

Instructions

Read one track's native MIDI note routing (input/output notes and scale transposition) from its MIDIMap. Reports unsupported explicitly when Live does not expose it.

Input Schema

Name	Required	Description	Default
`trackId`	Yes	ID from list_tracks.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.1Oct 23, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "input": {
+        "properties": {
+          "availableChannels": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "availableTypes": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "channel": {
+            "anyOf": [
+              {
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "type": {
+            "anyOf": [
+              {
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [],
+        "type": "object"
+      },
+      "monitoring": {
+        "anyOf": [
+          {
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "output": {
+        "properties": {
+          "availableChannels": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "availableTypes": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "channel": {
+            "anyOf": [
+              {
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "type": {
+            "anyOf": [
+              {
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [],
+        "type": "object"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Changed2 schema fields changedv0.3.0Oct 19, 2026

changedInput schema / properties / trackId / description

Previous value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavior: the source is the track's MIDIMap, and unsupported/unexposed routing is reported explicitly rather than silently omitted — useful error-contract context the annotations do not convey.

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?

Two tightly packed sentences with zero filler: the read scope and return contents come first, the edge-case contract second. Nothing is repeated from the schema or annotations.

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 single-parameter read tool with a full input schema, an output schema (so return values need no explanation) and complete annotations, the description covers purpose plus the unsupported-case behavior. Only the missing routing-vs-alternative disambiguation (e.g. against get_track_routing) keeps it short of complete.

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?

One parameter at 100% schema description coverage, so the schema fully documents trackId ('ID from list_tracks'). The description adds no syntax or semantics beyond that — the baseline 3 is correct when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb + resource + scope: 'Read one track's native MIDI note routing (input/output notes and scale transposition) from its MIDIMap.' The qualifier 'native MIDI note routing' and the enumeration of what it returns separate it from the broader get_track_routing and from its writer counterpart set_track_midi_routing, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use statement and no named alternative — unlike the strong calibration example, it never says 'for audio/track output routing use get_track_routing instead.' Guidance is only implied by the read-only 'get_' framing and the MIDI-routing specificity of the resource.

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

Deploy Server