Skip to main content
Glama

create_audio_clip

Load an audio file from an absolute path into an empty Session slot on a chosen audio track in Ableton Live 12.0.5+.

Instructions

Put an audio file into an empty Session slot of an audio track (Live 12.0.5 or newer).

Parameters:

  • track_index: An audio track

  • clip_index: The Session slot (must be empty)

  • path: Absolute path of the file (.wav, .aif, .mp3...)

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>",
      "path": "<path>"
    },
    "name": "create_audio_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
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?

No annotations are supplied, so the description carries the full burden. It does disclose two real behavioral constraints, the empty-slot precondition and the Live version floor, but says nothing about what happens on a non-empty slot, whether the file is copied or referenced, or whether the operation is undoable.

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

Conciseness4/5

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

The core action is front-loaded in one sentence, followed by a tight per-parameter list with no filler. Nothing is wasted, though the parameter list could be folded into a single line to be tighter still.

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?

An output schema exists, so return values need not be explained, and the three parameters are all described. The gaps are the index-base convention and the failure behavior for an occupied slot, which matter for a mutation tool with no annotations.

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 has to compensate, and it does: all three parameters get meaning beyond their titles, including that track_index is an audio track, clip_index must be empty, and path is an absolute file path with example formats. It omits whether indices are 0- or 1-based, which is the main remaining ambiguity.

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 gives a specific verb+resource: it inserts an audio file into a Session slot of an audio track, which clearly separates it from the clip-creation and arrangement siblings. It does not name an alternative tool, so sibling differentiation is only implicit.

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?

It states the key precondition (the Session slot must be empty) and a version requirement (Live 12.0.5+), which effectively says when the call will succeed. However, it gives no guidance on when to use this instead of e.g. create_clip, or what to do if the slot is already occupied.

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