Skip to main content
Glama

convert_audio

Converts Ableton Live audio clips into MIDI tracks, Simpler or Drum Rack setups, and moves slices or devices between tracks.

Instructions

The conversions behind Live's Convert menu. audio_to_midi: an audio clip becomes a MIDI clip on a new track (drums, melody or harmony). to_simpler: a new MIDI track with a Simpler holding the clip's sample. to_drum_rack: a new track with a Drum Rack, the sample on pad C1. slices_to_drum_rack: a sliced Simpler becomes a Drum Rack with a pad per slice. pad_to_track: a Drum Rack pad's chain gets its own MIDI track. move_devices_to_drum_rack: a track's devices move onto pad C1 of a new Drum Rack.

Live runs the conversion a moment after the answer, so use read_set afterwards to find the new track; track numbers after it may shift. MIDI clips and clips that are recording are refused. 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": {
      "action": "<action>"
    },
    "name": "convert_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNoFor audio_to_midi, to_simpler, to_drum_rack: the audio clip, t0/s2 (Session slot 2 of t0) or t0/a1 (second Arrangement clip of t0).
typeNoFor audio_to_midi: harmony, melody or drums.
trackNoFor move_devices_to_drum_rack: the track, t0, t1...
actionYesWhich conversion; see the tool description.
targetNoFor slices_to_drum_rack: a Simpler device address (t0/d0). For pad_to_track: a Drum Rack pad address (t0/d0/pC1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the asynchronous nature of the operation ('Live runs the conversion a moment after the answer'), a non-obvious side effect (track numbers may shift afterwards), input validity rules (MIDI and recording clips refused), and undo granularity ('One undo step'). None of these are inferable from readOnlyHint/destructiveHint/idempotentHint=false.

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?

It is front-loaded with purpose, then a per-action breakdown, then behavioral caveats — a sound ordering with no filler. The semicolon-compressed action list is information-dense but slightly harder to scan than a bulleted form, which keeps it just below top marks.

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

Completeness5/5

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

For a mutation tool with no output schema, the description compensates by telling the agent how to observe the result (read_set) and warning that positional addresses may shift. Combined with the refusal rules and undo semantics, nothing essential to calling this correctly is missing.

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 100%, and the parameter descriptions already map each of clip, type, target and track to the actions that consume them, including the t0/s2 and t0/d0/pC1 address formats. The prose largely repeats that mapping at the action level rather than adding new syntax or constraints, so the baseline of 3 applies.

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+resource (Live's Convert menu conversions) and then enumerates all six actions with the concrete outcome of each, e.g. 'to_drum_rack: a new track with a Drum Rack, the sample on pad C1' and 'pad_to_track: a Drum Rack pad's chain gets its own MIDI track'. An agent can tell exactly which conversion it wants without opening the 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?

It gives a clear post-call workflow ('use read_set afterwards to find the new track') and explicit when-not conditions ('MIDI clips and clips that are recording are refused'). It stops short of naming alternative siblings (e.g. create_track, load_device) that could achieve similar results, so there is no true alternative routing.

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