ableton-mcp

Overview Schema Source Related Servers Discussions Admin

plan_arrangement_repeat

Read-onlyIdempotent

Plan repeating an Ableton Arrangement passage across selected tracks into an empty destination window, preserving clip offsets and gaps, previewing boundaries/overlaps; each copy needs confirmation.

Instructions

Read an inventory map for repeating a whole Arrangement passage on explicit tracks into an empty destination window. Preserves relative clip offsets and gaps; reports boundary clips, destination content and planned overlaps. Up to 64 tracks, 512 source beats, 16 repeats and 256 placements. Non-atomic metadata preview, not a confirmation or content/automation verification. Each copy needs fresh guarded confirmation. All profile.

Input Schema

Name	Required	Description
`trackIds`	Yes	Exact ordinary source tracks; copy stays on each source track.
`repeatCount`	No	Contiguous repeats of the full source window; defaults to one.
`sourceEndBeats`	Yes	Exclusive source song beat; at most 512 beats after start.
`sourceStartBeats`	Yes	Inclusive source song beat.
`destinationStartBeats`	Yes	Start of a disjoint destination window in song beats.

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": {
+      "atomic": {
+        "const": false
+      },
+      "automationVerified": {
+        "const": false
+      },
+      "boundaryClips": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "canCopy": {
+        "type": "boolean"
+      },
+      "contentVerified": {
+        "const": false
+      },
+      "destinationClips": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "destinationRange": {
+        "type": "object"
+      },
+      "emptySource": {
+        "type": "boolean"
+      },
+      "emptyTrackIds": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "periodBeats": {
+        "type": "number"
+      },
+      "placements": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "plannedOverlaps": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "repeatCount": {
+        "type": "integer"
+      },
+      "requiresFreshConfirmation": {
+        "const": true
+      },
+      "setFingerprint": {
+        "type": "string"
+      },
+      "sourceRange": {
+        "type": "object"
+      },
+      "sources": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "stateVersion": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "tracks": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "stateVersion",
+      "setFingerprint",
+      "atomic",
+      "requiresFreshConfirmation",
+      "contentVerified",
+      "automationVerified",
+      "canCopy",
+      "emptySource",
+      "sourceRange",
+      "destinationRange",
+      "repeatCount",
+      "periodBeats",
+      "tracks",
+      "sources",
+      "placements",
+      "emptyTrackIds",
+      "boundaryClips",
+      "destinationClips",
+      "plannedOverlaps"
+    ],
+    "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

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description still adds real value: it discloses that relative clip offsets and gaps are preserved, that boundary clips, destination content and planned overlaps are reported, the hard limits (64 tracks, 512 beats, 16 repeats, 256 placements), that it is a non-atomic metadata preview lacking content/automation verification, and that each copy requires fresh confirmation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and dense with useful constraints, but phrasing is terse and jargon-heavy, and the trailing 'All profile.' is cryptic and unexplained, reducing readability.

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 need not be explained, yet the description still covers limits, safety workflow, and preview semantics. Full limits on repeat/placement counts are covered; only the odd closing phrase leaves ambiguity.

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 the baseline is 3. The description mostly restates schema bounds (tracks, beats, repeats) and adds only the semantic notion of an 'empty destination window', which the schema's destinationStartBeats description already conveys.

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 and resource: reads an inventory map for repeating a whole Arrangement passage into an empty destination window. The scope (explicit tracks, empty destination, whole passage) distinguishes it from generic clip placement, though it does not name a specific sibling alternative.

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?

Implies when to use it via preconditions (empty destination window, explicit ordinary source tracks, bounded repeat counts) and clarifies it is a preview needing fresh guarded confirmation per copy. It never explicitly directs the agent to a sibling tool such as duplicate_arrangement_clip or audition_arrangement_passage for related tasks.

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

Deploy Server