Skip to main content
Glama

create_audio_clip

Places an audio file on an audio track as a Session clip or at a timeline position. Use it to add audio clips to your Ableton Live Set.

Instructions

Put an audio file on an audio track as a Session clip (empty slot) or as a timeline clip (at_bar or at_beats). Say the clip's address and its audio details.

The track must be an audio track; MIDI tracks load samples through load_device. Only audio files are accepted. One undo step.

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

Input Schema

NameRequiredDescriptionDefault
clipNoSession slot by address instead of track and slot: t3/s0.
nameNoClip name. Empty: the file name.
pathYesAbsolute path of an audio file (wav, aif, aiff, flac, mp3, ogg, m4a, aac). ~ is expanded. Library samples: take the file path from your own file system, not the browser path.
slotNoSession: the empty slot (scene row) from 0, with track.
trackNoAn audio track, e.g. t3. Needed for a bar; with clip, optional.
at_barNoArrangement: place the clip at this bar (from 1) instead.
at_beatsNoArrangement: place the clip at this beat instead of a bar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/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-idempotent, non-destructive write, so the description adds real value beyond them by disclosing that the operation is one undo step and by constraining accepted input types. It does not say what happens if the target Session slot is already occupied or what the tool returns, which are material behavioral gaps for a creation tool.

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?

Short and front-loaded: the core action and its two modes come first, followed by constraints. The sentence "Say the clip's address and its audio details" is vague filler that does little work compared to the rest of the text.

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 7-parameter creation tool with no output schema and only partial annotation coverage, the description covers placement modes, input constraints, and undoability, which is most of what an agent needs to call it correctly. The lack of any statement about the result of the call or about slot-occupancy behavior is the remaining gap.

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 100%, so per-parameter meanings are already documented; the description earns credit only for explaining the addressing model that the individual parameters do not convey in isolation (either a clip address, or track plus slot for Session, or at_bar/at_beats for timeline). It adds no format or syntax detail beyond that, so the gain is modest.

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 (put an audio file as a clip) and enumerates the two distinct modes: a Session clip in an empty slot, or a timeline clip via at_bar/at_beats. It also names the sibling that handles the adjacent case (MIDI tracks load samples through load_device), so the agent can route correctly without opening other schemas.

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?

Gives clear when-to-use context for both modes and explicit preconditions: track must be an audio track, MIDI tracks go through load_device, only audio files are accepted. It stops short of naming alternatives for related operations on an already-existing clip (e.g. update_clip or write_clip), so a full 5 is not warranted.

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