Skip to main content
Glama

scene

Create, rename, duplicate, or capture scenes in Ableton Live sets. Set tempo, time signature, and color, or delete and launch scenes to organize a set in one undo step.

Instructions

Create a scene, rename it or set its tempo, time signature and color, duplicate it, or capture the playing clips into a new scene. Delete scenes with delete (target s2). Launch one with transport fire_scene. One undo step.

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": {
      "action": "<action>"
    },
    "name": "scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name.
indexNoFor create: where to insert, from 0. Empty: at the end.
sceneNoFor update and duplicate: number from 0 or exact name.
tempoNoScene tempo in BPM, or off. Empty: unchanged.
actionYescreate, update (rename, tempo, color), duplicate, capture.
color_indexNoLive's color number. Empty: unchanged.
time_signatureNoScene time signature such as 3/4, or off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is largely covered. The description adds one genuinely useful behavioral fact — 'One undo step' — but says nothing about permissions, what capture does to existing scenes, or whether duplicate copies settings.

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?

It is short and front-loads the primary operations before the sibling routing. The telegraphic phrasing ('Delete scenes with delete (target s2)') is efficient but slightly clipped, and the trailing 'One undo step' is a fragment.

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?

For a 7-parameter, multi-action tool with no output schema, the description covers all four actions and the two out-of-scope operations. It is complete enough to call correctly, though it could say more about what capture returns or how duplicate handles naming.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema, making 3 the baseline. The description adds only marginal meaning, mainly the 'target s2' hint for the delete sibling and the grouping of rename/tempo/color under update.

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 names a specific resource (scene) and enumerates the concrete operations: create, rename, set tempo/time signature/color, duplicate, capture playing clips. It also explicitly distinguishes itself from siblings by routing deletion to delete and launching to transport fire_scene.

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?

It gives explicit routing for two adjacent operations (delete scenes with delete, launch with transport fire_scene), which is exactly the when-to-use guidance an agent needs. It does not spell out when to choose capture versus duplicate, leaving that to the action enum.

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