ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_take_lane_context

Read-onlyIdempotent

Inspect a track's take-lane inventory or read a stored take clip without changing focus. Provide trackId; optionally add takeClipId for MIDI notes or audio timing details.

Instructions

Inspect one track take-lane inventory and optionally one complete stored take clip. Read-only; preserves focus. Selected MIDI reports up to 4096 notes; audio reports exposed source/timing controls. Does not expose comp selections, envelopes or rendered sound. All profile.

Input Schema

Name	Required	Description	Default
`trackId`	Yes	ID from list_tracks.
`takeClipId`	No	Exact take clip ID from this inventory; omit for lane/clip summaries.

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"
+      },
+      "lanes": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "source": {
+        "type": "object"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "status": {
+        "type": "string"
+      },
+      "supported": {
+        "type": "boolean"
+      },
+      "takeLanes": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "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.7/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 bar is lower; the description still adds real value with the 4096-note MIDI cap, the audio source/timing control reporting, and 'preserves focus'. The explicit negative scope (no comp selections, envelopes or rendered sound) prevents false expectations. It stops short of describing truncation behavior when the note cap is hit.

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?

Three tight sentences with the core purpose front-loaded and the exposure limits following logically. The trailing fragment 'All profile.' is ambiguous and spends a sentence's slot without conveying clear meaning.

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-value explanation is not required, and the description complements it by defining what is exposed and what is deliberately omitted. A prerequisite such as whether take lanes must be visible on the track would have made it fully complete for a two-parameter read tool.

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 coverage is 100% and both parameters carry their own descriptions, including 'omit for lane/clip summaries' for takeClipId, so the schema does the heavy lifting. The description adds only that the clip returned is 'complete', which is marginal beyond the schema.

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?

Specific verb 'Inspect' plus a precise dual resource: 'one track take-lane inventory and optionally one complete stored take clip'. It cleanly scopes what is and is not returned, though it never names the nearby siblings (get_take_lane_audition_context, show_take_lanes) to draw the boundary 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?

Usage is only implied: 'optionally one complete stored take clip' hints at when to supply takeClipId, and the exclusions hint at what questions this tool cannot answer. There is no explicit when-to-use/when-not statement or pointer to an alternative tool.

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

Deploy Server