ableton-mcp

Overview Schema Source Related Servers Discussions Admin

duplicate_clip

Copy an Ableton Live Session audio or MIDI clip into an empty compatible slot, defaulting to its source track, with guarded confirmation before execution.

Instructions

Copy a Session audio/MIDI clip into an empty compatible slot. Destination defaults to source track. Binds owners/layout and exposed content, rechecks at undo entry and reports explicit copy/name/preservation outcomes. Partial copies remain without cleanup/replay. Hidden state/envelopes/processing/file bytes not verified; audio shares its file. Updated bridge required.

Input Schema

Name	Required	Description
`name`	No	Optional copy name.
`clipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`dryRun`	No	False executes with token and hash.
`trackId`	Yes	ID from list_tracks.
`planHash`	No	Plan hash.
`confirmationToken`	No	Single-use plan token.
`destinationClipId`	Yes	list_clips Session ID or supported list_arrangement_clips ID.
`destinationTrackId`	No	Destination ordinary track ID; defaults to trackId. Must accept the source clip kind.
`expectedStateVersion`	Yes	Observed stateVersion.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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."

changedInput schema / properties / destinationClipId / 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: +[
+  {
+    "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"
+  }
+]

Changed10 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 / confirmationToken / description

Previous value: -"Short-lived, single-use token returned by the matching dry run."New value: +"Single-use plan token."

changedInput schema / properties / destinationClipId / 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."

addedInput schema / properties / destinationTrackId

Added value: +{
+  "description": "Destination ordinary track ID; defaults to trackId. Must accept the source clip kind.",
+  "type": "string"
+}

changedInput schema / properties / dryRun / description

Previous value: -"Omit or true to return a plan; false requires a valid confirmationToken."New value: +"False executes with token and hash."

changedInput schema / properties / expectedStateVersion / description

Previous value: -"Exact stateVersion observed immediately before planning."New value: +"Observed stateVersion."

addedInput schema / properties / name

Added value: +{
+  "description": "Optional copy name.",
+  "type": "string"
+}

changedInput schema / properties / planHash / description

Previous value: -"Hash returned by the matching dry run."New value: +"Plan hash."

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.6/5.0

Behavior4/5

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

The description adds substantial non-obvious behavior beyond the annotations: owner/layout binding, exposed content, undo-entry recheck, explicit outcome reporting, partial-copy behavior without cleanup or replay, unverified hidden state/envelopes/processing/file bytes, and file sharing for audio. The phrasing is dense and somewhat opaque, but it provides meaningful operational context that annotations alone do not cover.

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 purpose is front-loaded and the description is appropriately sized for a complex mutation tool. However, several sentences are telegraphic and jargon-heavy ('Binds owners/layout and exposed content'), and the important prerequisite 'Updated bridge required' is buried at the end.

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?

Given the output schema, the description does not need to explain return values and instead covers key operational caveats: partial copies, unverified hidden state/envelopes/processing/file bytes, shared audio file bytes, and bridge requirements. It is close to complete, though the prerequisite and failure semantics could be clearer.

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 schema already documents all nine parameters. The description adds contextual meaning for the destination ('empty compatible slot', 'defaults to source track') and notes that audio shares its file, but it does not explain the dry-run, plan-hash, confirmation-token, or state-version parameters beyond what the schema already states.

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?

The first sentence gives a specific verb and resource: copy a Session audio/MIDI clip into an empty compatible slot. The 'Session' qualifier helps distinguish it from arrangement-clip duplicates, though it does not explicitly name or rule out close siblings such as duplicate_clip_loop or duplicate_session_object.

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 by the 'empty compatible slot' condition, the default destination track, and the bridge requirement. However, there is no explicit comparison to sibling tools or statement of when to prefer this over duplicate_clip_loop, duplicate_session_object, or duplicate_arrangement_clip.

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

Deploy Server