ableton-mcp

Overview Schema Source Related Servers Discussions Admin

copy_clip

Copies a clip from one track and slot to an empty target track and slot, enabling loop reuse across scenes. The target must be empty, and MIDI clips require a MIDI target track.

Instructions

Copy the clip in track/slot to the empty slot to_track/to_slot, e.g. to reuse a loop in another scene. An occupied target is refused: delete_clip it first. A MIDI clip needs a MIDI target track.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track": "<track>",
      "slot": "<slot>",
      "to_track": "<to_track>",
      "to_slot": "<to_slot>"
    },
    "name": "copy_clip"
  }
}

Input Schema

Name	Required	Description	Default
`slot`	Yes
`track`	Yes
`to_slot`	Yes
`to_track`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Nov 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world operation. The description adds important behavior beyond annotations: the destination is checked and refused if occupied, and MIDI clips require a MIDI target track. It does not describe return behavior, but no output schema exists and the core failure modes are disclosed.

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

Conciseness5/5

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

The description is three compact sentences, front-loaded with the operation and immediately followed by its constraints. The example earns its place by clarifying intent, and there is no redundant wording.

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?

For a four-parameter copy operation with no output schema, the description covers the essential action, target precondition, failure workaround, and track-type compatibility. It is nearly complete, though it omits index-range or source-existence details that could matter in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden of explaining parameters. It clearly maps track/slot as the source and to_track/to_slot as the destination, and adds the constraint that the destination must be empty and type-compatible. It does not explain indexing or valid ranges, so it stops short of full parameter semantics.

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?

The description states a specific verb and resource: copy the clip from track/slot to to_track/to_slot. It also gives a concrete use case, reusing a loop in another scene, which distinguishes it from siblings like create_midi_clip, delete_clip, and play_clip.

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

Usage Guidelines5/5

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

It explicitly says the target must be empty and that an occupied target is refused, directing the agent to delete_clip first. It also states the MIDI-track compatibility rule, so the main when/when-not conditions are covered.

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