Skip to main content
Glama

set_clip_loop

Change a clip's loop switch, loop brace, and start/end markers in Ableton Live while preserving any values you omit.

Instructions

Change a clip's loop and markers; anything left out stays as it is.

With looping on, playback starts at start_marker and then repeats the brace (loop_start → loop_end); e.g. keep only the first bar of a 4-bar loop with loop_start=0, loop_length=4. With looping off Live plays loop_start → loop_end once, so markers given for such a clip are written to the brace. The writes are ordered so the start never passes the end; the reply shows what Live applied and lists any value it "adjusted". Switching warping off and on again resets an audio clip's warp markers.

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

  • location: "session" (default) or "arrangement"

  • looping: Loop switch

  • loop_start, loop_end: The brace (beats; seconds for unwarped audio)

  • loop_length: Alternative to loop_end: loop_end = loop_start + loop_length

  • start_marker, end_marker: Where playback starts and ends

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_clip_loop"
  }
}

Input Schema

NameRequiredDescriptionDefault
loopingNo
locationNosession
loop_endNo
clip_indexYes
end_markerNo
loop_startNo
loop_lengthNo
track_indexYes
start_markerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does well on mutation semantics: "anything left out stays as it is" establishes partial-update behavior, the write ordering ("start never passes the end") is disclosed, and the reply is said to list any value Live "adjusted" — an unusually honest disclosure of silent mutation. Gaps remain around permissions, failure modes for bad indices, and the warping note, which reads as a side-effect warning about a different tool rather than a behavior of this call.

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 lead sentence front-loads the operation and the partial-update contract, and the looping narrative is dense with real information rather than filler. The bracketed example earns its space by making the beat-based arithmetic concrete. Minor cost: the closing warping-marker sentence dangles without connecting to this tool's own parameters.

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 9-parameter mutation tool with no annotations and no schema descriptions, most of the load-bearing context is present: per-parameter meaning, units, defaults, the loop_length/loop_end relationship, partial-update semantics, write ordering, and response behavior. What is missing is error/edge behavior (invalid track_index or clip_index, what happens with unwarped audio if only markers are supplied), which matters given the zero annotation coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 9 parameters, so the description must compensate and largely does: units are given ("beats; seconds for unwarped audio"), clip_index is disambiguated ("Session slot, or position in get_arrangement_clips"), location's default is stated, loop_length is defined as loop_end = loop_start + loop_length, and a concrete worked example ties loop_start/loop_length to a musical outcome. Only the two required index parameters get a one-line gloss with no range or validity information.

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?

"Change a clip's loop and markers" names a specific verb and resource and immediately enumerates the affected attributes (loop brace, start/end markers). The verb "Change" plus the loop/marker scope cleanly separates it from the read-side sibling get_clip_loop and from set_clip_warp, which owns warping rather than the brace.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative, so an agent has to infer usage from the parameter semantics and the looping on/off explanation. The looping-on vs looping-off narrative does imply which parameters matter in each state, which makes the guidance workable but implied rather than stated.

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