Skip to main content
Glama

start_playback

Starts Ableton Live playback from the current playhead position so AI assistants can audition arrangements and MIDI parts. Use it to begin transport playback before listening or analyzing.

Instructions

Start the transport (plays from the playhead).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_playback"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. The parenthetical "plays from the playhead" is a genuinely useful behavioral detail about where playback resumes, but nothing is said about whether an existing playing state is affected, whether the call is idempotent, or what the returned state represents.

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?

A single short sentence, front-loaded with the action and supplemented by a tight parenthetical that adds real information. Nothing is wasted or buried.

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?

This is a trivially simple zero-parameter tool with an output schema that carries the return-state detail, so the description is nearly sufficient as-is. The remaining gap is the lack of any contrast with stop_playback or clip/scene firing, which matters slightly more for a transport control than for a data tool.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

States a specific verb and resource ("start the transport" / play), and the parenthetical disambiguates that playback begins at the current playhead rather than from the beginning. It does not explicitly distinguish itself from siblings like fire_clip or fire_scene, which also initiate playback at a more granular level, so it stops short of a 5.

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 at all. The description never mentions stop_playback as the counterpart, nor does it clarify when to use transport-level playback versus firing a clip or scene, so an agent must infer the routing from names alone.

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