Skip to main content
Glama

play

Idempotent

Start Ableton Live transport and read back the is_playing status to confirm playback is running. Optionally set the playhead to a specific beat or resume from the current position before starting.

Instructions

Start transport playback and read back the is_playing status.

Returns:
    Dictionary reporting the start call and the read-back is_playing flag.

Note:
    The read-back proves the transport is running, not that anything is audible:
    a muted track, an empty Arrangement or a track with no instrument all play
    silently. Use stop to halt, and set_arrangement_time to move the playhead
    without starting.

    Leave the transport as it was found. Nothing here stops it on its own, and a
    set left playing keeps playing for whoever is at the machine.

    A Session clip that has played leaves its track in Session view, and the
    track then ignores the Arrangement until Live's Back to Arrangement button
    is pressed. ``song.back_to_arranger`` reports that state and cannot clear
    it: measured 2026-09-07 against Live 12.4.5, writing it false reads back
    ``not_observed`` and the value stays true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_beatNoCue the playhead to this beat before starting, in beats from the start of the Arrangement. Omit to start from wherever the playhead already sits.
continue_playingNoTrue resumes from the current position instead of restarting. Ignored when from_beat is given, since that sets the position.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / continue_playing / description
      Added value: +"True resumes from the current position instead of restarting. Ignored when from_beat is given, since that sets the position."
    • addedInput schema / properties / from_beat / description
      Added value: +"Cue the playhead to this beat before starting, in beats from the start of the Arrangement. Omit to start from wherever the playhead already sits."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral traits: the read-back proves transport running but not audibility, the transport is left as found, nothing stops it automatically, and a played Session clip can change Arrangement behavior until back_to_arranger is pressed. This substantially exceeds what the annotations already provide.

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 description is organized into clear sections: purpose, return value, and behavioral notes. It is longer than a minimal description, but each paragraph earns its place by conveying non-obvious information. Only minor trimming would be possible without losing value.

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

Completeness5/5

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

The description is thorough for a transport-control tool with an output schema and annotations. It covers side effects, edge cases, alternative tools, and state transitions, so an agent has enough context to decide when to invoke it and what to expect afterward.

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

Parameters3/5

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

The schema covers both parameters with full descriptions, so the description does not need to repeat parameter semantics. The description does add context about from_beat by mentioning set_arrangement_time as an alternative way to move the playhead, but that is more usage guidance than parameter semantics. Schema coverage is 100%, so baseline 3 is appropriate.

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 states a specific verb and resource: 'Start transport playback' and read back is_playing. It clearly distinguishes the tool's function from related siblings by naming stop and set_arrangement_time as alternatives, and by describing its return value.

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

Usage Guidelines5/5

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

The description gives explicit routing guidance: 'Use stop to halt, and set_arrangement_time to move the playhead without starting.' It also warns about the Session-clip behavior and the Back to Arrangement button, so the agent knows when this tool is appropriate and what follow-up actions may be needed.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server