ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_clip_mixer_envelope

Read-onlyIdempotent

Read a Session clip's volume, stereo pan, or exact Return-send envelope without changing focus or playback; supports MIDI and warped audio beats.

Instructions

Read an ordinary Session clip volume, Stereo pan or exact Return-send envelope without changing focus or playback. MIDI/warped audio beats. Pan requires known Stereo mode. Samples do not recover the complete curve.

Input Schema

Name	Required	Description
`clipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`sendId`	No	Required for send; exact ID from get_track_mixer. Omit for volume or pan.
`trackId`	Yes	ID from list_tracks.
`sampleTimes`	No	Optional native probes.
`mixerControl`	Yes	Track fader, Stereo pan or exact track-to-Return send. Pan refuses Split Stereo or unknown modes.
`returnTrackId`	No	Required for send; matching Return ID from get_track_mixer. Omit for volume or pan.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.3.1Oct 23, 2026

changedInput schema / properties / clipId / description

Previous value: -"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."New value: +"list_clips Session ID or supported list_arrangement_clips ID."

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

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "clipId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "exists": {
+        "type": "boolean"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "samples": {
+        "items": {
+          "properties": {
+            "time": {
+              "type": "number"
+            },
+            "value": {
+              "type": "number"
+            }
+          },
+          "required": [
+            "time",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "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 readOnlyHint/idempotentHint/non-destructive, so the bar is lower. The description adds genuinely useful context beyond them: it changes neither focus nor playback, beat semantics are MIDI/warped-audio based, pan refuses Split Stereo, and sampling does not reconstruct the full curve. These caveats materially help an agent avoid misuse.

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-loads the core purpose and keeps every sentence load-bearing with no filler. Some fragments ('MIDI/warped audio beats.') are telegraphic and slightly cryptic, costing a little clarity but not wasting 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?

With an output schema present, annotations covering safety, and full schema coverage, the description need not explain returns. It supplies the key caveats (mode requirements, sampling limits, no focus/playback change), leaving only alternative-selection guidance thin.

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 100% so the baseline is 3, but the description adds real meaning: 'exact Return-send' clarifies the sendId/returnTrackId pairing, 'Pan requires known Stereo mode' constrains the pan enum value, and the sampling caveat contextualizes sampleTimes. It goes modestly 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?

States a specific verb ('Read') and resource ('Session clip volume, Stereo pan or exact Return-send envelope'), making scope concrete enough to separate it from device-parameter envelopes. It doesn't name sibling tools like get_clip_parameter_envelope to sharpen the contrast, so it falls short of a 5.

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?

Provides prerequisites ('Pan requires known Stereo mode') and a caveat ('Samples do not recover the complete curve') that imply when it works and when it doesn't. However, it gives no explicit guidance on when to choose this over alternatives or how to handle the unsupported cases, leaving usage mostly implied.

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

Deploy Server