ableton-mcp

Overview Schema Source Related Servers Discussions Admin

copy_arrangement_clip_to_track

Copies an exact Arrangement MIDI or audio clip to a compatible ordinary track at a specified empty interval and new name, then verifies the actual copy.

Instructions

Copy one exact Arrangement MIDI or audio clip onto another compatible ordinary track at an explicit empty interval and name. Binds native owners, layouts and exposed source content, rechecks at undo entry and verifies actual copy readback. Retains partial work without rollback or replay. Does not copy devices, routing or hidden/envelope state; audio shares its source file. Updated bridge; all profile.

Input Schema

Name	Required	Description
`name`	Yes	Explicit new clip label without controls.
`clipId`	Yes	Exact track-N:arrangement-clip-M source ID.
`dryRun`	No	False executes with token and hash.
`trackId`	Yes	ID from list_tracks.
`planHash`	No	Plan hash.
`startBeats`	Yes	Nonnegative destination beat; entire observed source span must be empty.
`confirmationToken`	No	Single-use plan token.
`destinationTrackId`	Yes	ID from list_tracks.
`expectedStateVersion`	Yes	Observed stateVersion.

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: +[
+  {
+    "oneOf": [
+      {
+        "properties": {
+          "confirmation": {
+            "properties": {
+              "expiresAt": {
+                "type": "number"
+              },
+              "planHash": {
+                "pattern": "^[a-f0-9]{64}$",
+                "type": "string"
+              },
+              "token": {
+                "minLength": 1,
+                "type": "string"
+              }
+            },
+            "required": [
+              "token",
+              "planHash",
+              "expiresAt"
+            ],
+            "type": "object"
+          },
+          "dryRun": {
+            "const": true
+          },
+          "plan": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "plan",
+          "confirmation"
+        ],
+        "type": "object"
+      },
+      {
+        "properties": {
+          "dryRun": {
+            "const": false
+          },
+          "operationOutcome": {
+            "properties": {
+              "evidence": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "reason": {
+                "type": "string"
+              },
+              "schemaVersion": {
+                "const": 1
+              },
+              "status": {
+                "enum": [
+                  "applied",
+                  "outcome_unknown",
+                  "postconditions_failed",
+                  "pending_postconditions",
+                  "pending_user_action"
+                ]
+              }
+            },
+            "required": [
+              "schemaVersion",
+              "status",
+              "reason",
+              "evidence"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "dryRun",
+          "operationOutcome"
+        ],
+        "type": "object"
+      }
+    ],
+    "properties": {
+      "dryRun": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "dryRun"
+    ],
+    "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

A4/5.0

Behavior5/5

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

Goes well beyond annotations: discloses what is NOT copied (devices, routing, hidden/envelope state), that audio shares its source file, that it verifies readback and rechecks at undo entry, and that partial work is retained without rollback — genuinely useful behavioral context for a non-idempotent mutation.

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?

The first sentence is front-loaded and precise, but subsequent sentences are dense and cryptic ('Binds native owners, layouts and exposed source content', 'Updated bridge; all profile') that read as jargon rather than clear guidance, costing 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?

An output schema exists so return values need not be described, and annotations cover the safety profile. The description adds scope, exclusions, verification, and partial-failure behavior — nearly complete, though the opaque 'all profile'/'updated bridge' phrasing leaves a minor 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%, so the schema documents all parameters including clipId, startBeats, name, and the confirmationToken/planHash/dryRun plan flow. The description only reinforces the empty-interval and explicit-name semantics without adding syntax or format details, so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (copy an Arrangement MIDI or audio clip) and the destination constraint (onto another compatible ordinary track at an explicit empty interval), which distinguishes it from in-place siblings like duplicate_arrangement_clip or move_arrangement_clip without naming them.

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?

Preconditions are stated clearly (compatible ordinary track, explicit empty interval, explicit name), implying when the tool applies. However, no alternatives or when-not guidance are explicit — it never says 'use duplicate_arrangement_clip for in-place' or names a sibling to route away from.

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

Deploy Server