Skip to main content
Glama

start_playback

Initiates playback of the current Ableton Live session, allowing AI-assisted music production to begin.

Instructions

Start playing the Ableton session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'start_playback'. Connects to Ableton remote script and sends the 'start_playback' command via socket communication.
    def start_playback(ctx: Context) -> str:
        """Start playing the Ableton session."""
        try:
            ableton = get_ableton_connection()
            result = ableton.send_command("start_playback")
            return "Started playback"
        except Exception as e:
            logger.error(f"Error starting playback: {str(e)}")
            return f"Error starting playback: {str(e)}"
  • Actual implementation in Ableton remote script that invokes Live's song.start_playing() API to start playback.
    def _start_playback(self):
        """Start playing the session"""
        try:
            self._song.start_playing()
            
            result = {
                "playing": self._song.is_playing
            }
            return result
        except Exception as e:
  • Registration of 'start_playback' as a state-modifying command in the remote script's command dispatcher, which schedules it on the main thread.
    elif command_type in ["create_midi_track", "set_track_name", 
                         "create_clip", "add_notes_to_clip", "set_clip_name", 
                         "set_tempo", "fire_clip", "stop_clip",
                         "start_playback", "stop_playback", "load_browser_item"]:
  • Helper list identifying 'start_playback' as a modifying command that requires delays during socket communication.
    is_modifying_command = command_type in [
        "create_midi_track", "create_audio_track", "set_track_name",
        "create_clip", "add_notes_to_clip", "set_clip_name",
        "set_tempo", "fire_clip", "stop_clip", "set_device_parameter",
        "start_playback", "stop_playback", "load_instrument_or_effect"
  • Dispatch/registration point in remote script where 'start_playback' command is routed to the _start_playback handler.
    elif command_type == "start_playback":
        result = self._start_playback()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Start playing') but doesn't explain what 'playing' entails (e.g., starts from current position, requires a session to be loaded, may affect other playback states), or any side effects like audio output or session state changes.

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?

The description is a single, direct sentence with no wasted words, making it highly concise and front-loaded. Every part of the sentence ('Start playing the Ableton session') contributes essential information without redundancy.

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?

Given the tool's complexity (a playback control with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, success/failure conditions, or what 'playing' means in context, leaving significant gaps for an AI agent.

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 has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately avoids mentioning any, earning a baseline high score for this dimension.

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 clearly states the action ('Start playing') and the target resource ('the Ableton session'), making the purpose immediately understandable. It doesn't differentiate from its sibling tool 'stop_playback', but it's specific enough to avoid vagueness or tautology.

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?

No guidance is provided on when to use this tool versus alternatives like 'stop_playback' or other playback-related tools. The description lacks context about prerequisites, timing, or exclusions, leaving usage entirely implicit.

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

Install Server

Other Tools

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/ahujasid/ableton-mcp'

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