Skip to main content
Glama
Sign In
Ableton MCP Extended

Ableton MCP Extended

by RichieMiller-HU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_clip_loop

Adjust loop and marker positions for a clip in Ableton Live, enabling or disabling looping and setting start/end points in beats.

Instructions

Set a clip's loop and start/end marker properties (in beats). Only the parameters you pass are changed.

Parameters:

  • track_index / clip_index: which clip

  • looping: enable/disable looping

  • loop_start / loop_end: loop brace positions in beats

  • start_marker / end_marker: clip play start/end in beats

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
loop_endNo
clip_indexYes
end_markerNo
loop_startNo
track_indexYes
start_markerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It discloses the behavior (setting loop/markers, partial updates, units in beats) but lacks details on side effects, permissions, or reversibility. Adequate although more specificity would help.

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

Conciseness5/5

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

Description is very concise: one sentence for purpose, one for behavior, then a bullet list of parameters. No wasted words, front-loaded with main action.

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?

Given that an output schema exists (not shown), return values need not be described. The description covers the core functionality, partial updates, and parameter units. However, it omits constraints like value ranges or interaction with other clip properties.

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 description coverage is 0%, so description must compensate. It explains each parameter with purpose (e.g., 'which clip', 'enable/disable looping', positions in beats). This adds value beyond the schema's names/types.

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 clearly states 'Set a clip's loop and start/end marker properties (in beats).' This is a specific verb-resource combination that distinguishes it from siblings like fire_clip, stop_clip, or set_clip_name.

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?

The description includes 'Only the parameters you pass are changed,' implying partial updates. It implicitly tells when to use (to modify loop/marker properties) but does not explicitly mention alternatives or when not to use.

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