Skip to main content
Glama
Sign In
ableton-mcp

ableton-mcp

by ok2ju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_clip

Starts playback of a chosen clip slot in Ableton Live, automatically starting the transport if it is stopped.

Instructions

Start playing the clip in this slot. Live starts the transport if it is stopped.

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": "<track>",
      "slot": "<slot>"
    },
    "name": "play_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYes
trackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations only declare it is not read-only, not destructive, and closed-world. The description adds a genuinely non-obvious side effect beyond that: the transport auto-starts if it is currently stopped. It does not say whether other clips on the track stop, or what happens if the slot is empty, so it falls short of full disclosure.

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?

Two tight sentences with the action front-loaded and no filler. The second sentence is slightly cryptic in referring to 'Live' without context, but the information density is high.

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

Completeness2/5

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

With no output schema and zero parameter documentation, the description carries the full burden and does not finish the job. It omits how to address track/slot and what the tool returns, which are exactly the gaps an agent needs filled before calling it.

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

Parameters2/5

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

Schema description coverage is 0% for both required parameters. The description mentions 'this slot' but says nothing about the track parameter, indexing base (0- vs 1-based), or valid ranges, so an agent must guess how to address a clip.

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

Purpose4/5

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

The description gives a specific verb and resource: 'Start playing the clip in this slot.' It is clearly a playback trigger, distinguishable in spirit from siblings like stop and fire_scene, but it never names or contrasts those siblings explicitly.

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?

Usage is only implied: the agent infers this is the tool to start a clip's playback. There is no statement of when not to use it, no prerequisites, and no reference to alternatives such as fire_scene for triggering a whole scene or live_status for checking transport state.

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