ableton-mcp

Overview Schema Source Related Servers Discussions Admin

plan_midi_transposition

Read-onlyIdempotent

Plan exact chromatic transposition of stable MIDI note IDs by semitones while preserving all non-pitch note state in an Ableton Live clip.

Instructions

Plan exact chromatic transposition of stable MIDI note IDs while preserving all non-pitch note state.

Input Schema

Name	Required	Description
`clipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`noteIds`	Yes	Unique stable note IDs to transpose.
`trackId`	Yes	ID from list_tracks.
`semitones`	Yes	Signed non-zero chromatic transposition in semitones.

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": {
+        "type": "string"
+      },
+      "context": {
+        "type": "object"
+      },
+      "plan": {
+        "properties": {
+          "changes": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "newNotes": {
+            "items": {
+              "properties": {
+                "duration": {
+                  "type": "number"
+                },
+                "pitch": {
+                  "maximum": 127,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "start": {
+                  "type": "number"
+                },
+                "velocity": {
+                  "maximum": 127,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "pitch",
+                "start",
+                "duration",
+                "velocity"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "noteIds": {
+            "items": {
+              "type": "integer"
+            },
+            "type": "array"
+          },
+          "notes": {
+            "items": {
+              "properties": {
+                "duration": {
+                  "type": "number"
+                },
+                "pitch": {
+                  "maximum": 127,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "start": {
+                  "type": "number"
+                },
+                "velocity": {
+                  "maximum": 127,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "pitch",
+                "start",
+                "duration",
+                "velocity"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "preservedNotes": {
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [],
+        "type": "object"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "trackId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "trackId",
+      "clipId",
+      "context",
+      "plan"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "outcome": {
+            "enum": [
+              "unknown",
+              "not_executed"
+            ]
+          }
+        },
+        "required": [
+          "message",
+          "outcome"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedv0.3.0Oct 19, 2026

changedInput schema / properties / clipId / description

Previous value: -"Stable clip ID: track-N:clip-M from list_clips, or track-N:arrangement-clip-M from list_arrangement_clips for tools that support Arrangement clips."New value: +"Session ID from list_clips; Arrangement ID from list_arrangement_clips where supported."

changedInput schema / properties / trackId / description

Previous value: -"Stable track ID returned by list_tracks."New value: +"ID from list_tracks."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: only pitch changes while 'all non-pitch note state' (velocity, timing, etc.) is preserved. It does not explain the plan/apply handoff, but with annotations present the bar is lower.

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?

A single tight sentence, front-loaded on the verb and resource, with no filler. It is arguably undersized for a four-parameter planning tool, but nothing in it 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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description is complete enough to call the tool correctly, though it omits the workflow relationship to apply_midi_transposition and plan_midi_diatonic_transposition.

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% and every parameter is documented in-schema (including the non-zero semitone constraint and stable note ID semantics). The description adds only the notion of 'exact chromatic' transposition, 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 (plan), a specific resource (chromatic transposition of MIDI note IDs), and a distinctive constraint (preserving all non-pitch note state). The word 'chromatic' implicitly contrasts with the diatonic sibling, but no sibling tool is named explicitly, so the differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The agent must infer from the name alone that this 'plan' step precedes apply_midi_transposition and that plan_midi_diatonic_transposition is the in-scale alternative; the description says nothing about either.

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

Deploy Server