ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_return_routing

Read-onlyIdempotent

Read a Return Track's output destination and available routing choices without changing routing, selection, or playback; unavailable properties are reported.

Instructions

Read the exact output destination and available choices of one Return Track without changing routing, selection or playback. Reports unavailable native properties explicitly; send pre/post mode is not exposed.

Input Schema

Name	Required	Description	Default
`returnTrackId`	Yes	Canonical return-N ID from get_set_mixer.

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"
+      },
+      "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"
+          }
+        ]
+      },
+      "returnTrackId": {
+        "type": "string"
+      },
+      "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"
+  }
+]

Addedv0.3.0Oct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description adds real value beyond them: it discloses that unavailable native properties are reported explicitly and that send pre/post mode is not exposed. That caveat heads off an agent assuming an incomplete payload is an error.

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 written sentences with zero waste. The read-only guarantee is front-loaded, and the payload caveat follows it in one compact clause.

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?

With an output schema present, the description need not explain return values, and it covers the main behavioral surprises (non-mutating, explicit unavailability reporting, missing pre/post mode). What remains thin is guidance on its relationship to other routing readers, a minor gap.

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?

There is a single parameter with 100% schema description coverage; the schema already says it takes the canonical return-N ID from get_set_mixer. The description adds no further format or validation detail, so baseline 3 applies.

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 ('read') and a precisely scoped resource: the output destination and available choices of one Return Track. It separates itself from mutation siblings like set_return_mixer and set_track_routing by emphasizing that no routing, selection or playback changes occur, though it never names an alternative read tool (e.g. get_track_routing) directly.

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?

The read-only framing implies when to use it, and the scope is limited to a single return track, but there are no explicit when/when-not statements or references to sibling tools for regular tracks or for changing routing. Usage is inferable rather than stated.

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

Deploy Server