Skip to main content
Glama

delete_arrangement_clip

Remove a clip from an Ableton Arrangement track and shift later clips down one index. Use track_index and clip_index to target the exact clip.

Instructions

Remove a clip from the Arrangement. Later clips on the track move down one index.

Parameters:

  • track_index: The track

  • clip_index: Position of the clip in get_arrangement_clips

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_index": "<track_index>",
      "clip_index": "<clip_index>"
    },
    "name": "delete_arrangement_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the side effect that later clips on the track shift down one index, but it omits whether deletion is irreversible, what permissions are required, or whether undo is possible.

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 definition is front-loaded with the action and its side effect, followed by a compact parameter list. Every sentence adds useful information with no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema is present and the index-shift side effect is documented, which covers important behavior. Still, for a destructive operation with no annotations, the definition should ideally state irreversibility, permission needs, or confirmation expectations.

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 0%, so the description must compensate. It clarifies that clip_index is a position from get_arrangement_clips, which is valuable, but track_index is only described as 'The track' and remains underspecified as an integer index.

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 description states a specific verb and resource ('Remove a clip from the Arrangement'), and the Arrangement scope helps distinguish it from the sibling delete_clip. It stops short of explicitly naming the alternative or clarifying whether delete_clip handles session clips.

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 through the parameter notes: clip_index is defined relative to get_arrangement_clips, suggesting that tool should be called first. However, there is no explicit when-to-use vs when-not-to-use guidance or direct comparison with delete_clip.

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

Deploy Server

Other Tools