Skip to main content
Glama

create_clip

Creates an empty MIDI clip in an empty Session slot on a chosen track, setting its length in beats to start composing or arranging directly in Ableton Live.

Instructions

Make an empty MIDI clip in a Session slot (the slot must be empty).

Parameters:

  • track_index: A MIDI track

  • clip_index: The Session slot (scene row)

  • length: Clip length in beats (default 4 = one bar in 4/4)

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": "create_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNo
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.2/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 and does disclose the key trait that the clip is created empty and the slot must be vacant. It does not say what happens if the slot is occupied, whether the track must be a MIDI track rather than audio, or whether the operation is reversible — all relevant for an unannotated mutation.

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?

One front-loaded sentence states the action and constraint, followed by a tight bulleted parameter list. Every line adds information and nothing is redundant.

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 simple three-parameter creation tool with an output schema present (so return values need not be described), the definition covers purpose, precondition, and all parameters. Minor gaps around failure behavior on an occupied slot or non-MIDI track keep it from being fully complete.

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 description coverage is 0%, and the description compensates by mapping each of the three parameters to meaning: track_index as a MIDI track, clip_index as the Session slot/scene row, and length in beats with the default 4 equal to one bar in 4/4. Only the allowed ranges or index bounds remain undocumented.

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 ('Make an empty MIDI clip') plus location and precondition ('in a Session slot (the slot must be empty)'). This distinguishes it from create_audio_clip and create_scene without needing to open any schema.

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

Usage Guidelines4/5

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

The precondition that the target slot must be empty gives clear context for when the call will succeed. It never names an explicit alternative or exclusion (e.g. use add_notes_to_clip to populate it afterwards), so it falls short of explicit when-not guidance.

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