LiveSession MCP

Overview Schema Source Related Servers Discussions Admin

set_audio_clip

Adjust an audio clip's gain, warping mode, pitch, and name to refine playback or arrangement in Ableton Live.

Instructions

Audio clip settings: gain (0-1), warping, warp_mode (beats, tones, texture, re-pitch, complex, complex pro — use complex pro for vocals/full mixes), pitch in semitones/cents, name.

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

Input Schema

Name	Required	Description	Default
`gain`	No
`name`	No
`warping`	No
`warp_mode`	No
`clip_index`	Yes
`pitch_fine`	No
`arrangement`	No
`track_index`	Yes
`pitch_coarse`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 7, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare the safety profile (not read-only, not destructive, closed-world), so the description only needs incremental behavior. It adds the gain range (0-1) and a concrete set of warp_mode values with a recommendation for 'complex pro', which is genuinely useful. It does not disclose the key partial-update semantics, i.e. whether omitted fields are left unchanged or reset, which matters for a 9-parameter setter with mostly optional args.

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

Conciseness3/5

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

It is compact with no filler, but it is one run-on colon-list with no leading verb and no sentence structure, so the 'complex pro' aside is buried mid-list. Dense but not front-loaded around what the tool actually does.

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 annotations cover safety. What is missing for a 9-parameter mutation tool is how the target clip is addressed (track_index/clip_index), what the 'arrangement' flag switches, and whether the call is a partial patch or a full overwrite.

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% with no enums declared, so the description carries the whole burden and does real work: it supplies the gain domain, the exact warp_mode value vocabulary, and the semitone/cents meaning of the two pitch parameters. Three parameters (track_index, clip_index, arrangement) are never mentioned and index-based addressing is unexplained, which keeps it below 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase field list ('Audio clip settings: gain, warping, warp_mode, pitch, name') rather than a verb+resource statement, so the mutating action must be inferred from the tool name. It is clear what domain it touches, but it never says it writes these values to an existing audio clip, and it does not distinguish itself from siblings such as transpose_clip or set_clip_name that overlap with its pitch and name fields.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. An agent cannot tell from this text whether to use set_audio_clip or transpose_clip for pitch, or set_clip_name for renaming, despite name and pitch both being offered here.

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

Deploy Server