ableton-mcp

Overview Schema Source Related Servers Discussions Admin

get_midi_note_insertion_context

Read-onlyIdempotent

Retrieve notes, timing, and edit safety context for a single MIDI clip before inserting notes; read-only, up to 4096 notes without sampling.

Instructions

Read complete notes, timing, native identity and edit safety for adding notes to one Session/Arrangement MIDI clip. Read-only, up to 4096 notes without sampling; 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"
+          }
+        ]
+      },
+      "clipTiming": {
+        "type": "object"
+      },
+      "deviceId": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "editContext": {
+        "type": "object"
+      },
+      "identityToken": {
+        "type": "string"
+      },
+      "insertSupported": {
+        "type": "boolean"
+      },
+      "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"
+          }
+        ]
+      },
+      "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.7/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the safety bar is met elsewhere; the description adds genuine extra context by disclosing the read is unsampled and complete up to 4096 notes and covers the 'all profile' scope. This tells the agent the returned note set is exhaustive, which the annotations do not.

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-loaded with what is read, then scope, then the limit/read-only qualifiers — efficient and short. The trailing fragment 'all profile' is compressed to the point of ambiguity, a minor cost.

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 and annotations declaring the safety profile, the description only needs to frame scope and read guarantees, which it does (single clip, up to 4096 notes, no sampling). It stops short of explaining what 'edit safety' or 'native identity' convey to the caller, leaving the main conceptual 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?

Schema coverage is 100% and both required parameters (trackId, clipId) are documented in the schema itself, so the description only reinforces scope ('one Session/Arrangement MIDI clip'). No added meaning about ID formats or constraints beyond what the schema states. Baseline 3.

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 concrete verb and resource ('Read complete notes, timing, native identity and edit safety') scoped to one Session/Arrangement MIDI clip. The 'for adding notes' qualifier separates it from the plain note-reading siblings like get_midi_clip_notes, though the phrase 'native identity' and 'edit safety' remain opaque without opening the output schema.

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 mention of 'for adding notes' implies this is the pre-flight read before insert_midi_notes, but no sibling or alternative is named and no condition for choosing it over get_midi_clip_notes / get_midi_clip_notes_extended / get_midi_note_removal_context is given. 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