ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_midi_note_selection

Read-onlyIdempotent

Retrieve selected MIDI note IDs and properties from a specific Ableton Live Session or Arrangement clip without changing focus, plus a token for guarded property updates.

Instructions

Read stable native note selection for one exact current detail Session/Arrangement MIDI clip without moving focus or selecting notes. Returns selected IDs/properties and a token for optional set_midi_note_properties guarding. Empty, unavailable and not-detail-clip are distinct. Up to 4096 selected notes, no truncation; all profile.

Input Schema

Name	Required	Description	Default
`clipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`trackId`	Yes	ID from list_tracks.

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"
+          }
+        ]
+      },
+      "editContext": {
+        "type": "object"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "noteIds": {
+        "items": {
+          "type": "integer"
+        },
+        "type": "array"
+      },
+      "notes": {
+        "items": {
+          "properties": {
+            "duration": {
+              "type": "number"
+            },
+            "mute": {
+              "type": "boolean"
+            },
+            "noteId": {
+              "type": "integer"
+            },
+            "pitch": {
+              "maximum": 127,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "probability": {
+              "maximum": 1,
+              "minimum": 0,
+              "type": "number"
+            },
+            "releaseVelocity": {
+              "maximum": 127,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "start": {
+              "type": "number"
+            },
+            "velocity": {
+              "maximum": 127,
+              "minimum": 0,
+              "type": "integer"
+            },
+            "velocityDeviation": {
+              "type": "integer"
+            }
+          },
+          "required": [
+            "noteId",
+            "pitch",
+            "start",
+            "duration",
+            "velocity",
+            "mute"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "reason": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "selectionToken": {
+        "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.9/5.0

Behavior5/5

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

Beyond the annotations (which already declare read-only/idempotent/non-destructive), it discloses that it returns IDs/properties plus a guard token, distinguishes empty vs unavailable vs not-detail-clip states, and states a 4096-note ceiling with no truncation. That is substantive behavioral context the annotations do not carry.

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 action and read-only guarantee, then layers return/limit details efficiently. A few telegraphic fragments ('all profile') cost a little clarity but nothing is wasted.

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, return values needn't be spelled out, and the description still covers the guard token, distinct edge-case states, and the 4096 cap. Nearly complete for a 2-param read tool; minor missing detail about what 'properties' includes.

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 description coverage is 100%, so both trackId and clipId are already documented in the schema. The description adds no param-level meaning beyond what the schema provides, so the 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 resource (stable native note selection) scoped to one exact current detail MIDI clip, and the phrase 'without moving focus or selecting notes' distinguishes it from selection-mutating tools. Slightly jargon-heavy ('detail clip') and does not name a sibling alternative explicitly, keeping it below 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?

Usage is implied rather than stated: the read-only snapshot framing plus the mention of a token 'for optional set_midi_note_properties guarding' signals when this is useful, but it never says when to prefer this over get_midi_clip_notes or get_selection_context.

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

Deploy Server