Skip to main content
Glama
Sign In
Ableton MCP for Live Intro

Ableton MCP for Live Intro

by untitledxdamage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_scene

Add a scene row to a Live 12 Intro set. Appends to the bottom by default, or inserts at a chosen index with an optional name to organize Session view playback.

Instructions

Add a scene (row). index=-1 appends at the bottom.

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": "create_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the default append behavior (index=-1) but says nothing about what a newly created scene looks like, whether the name is auto-generated when null, or what happens if index is out of range.

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 short sentences with the core action front-loaded and no filler. It is appropriately sized, though the brevity comes partly from what it omits rather than pure efficiency.

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?

For a 2-parameter mutation tool with no annotations and no output schema, the description leaves significant gaps: the meaning of a null name, the return value, and error/edge behavior for index are all unaddressed.

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 0%, so the description must compensate. It usefully explains the index parameter's default sentinel (-1 appends at bottom), which the schema only states as a bare default. However, it says nothing about the name parameter's null default or auto-naming behavior.

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 ('Add a scene'), and the parenthetical '(row)' clarifies the domain concept of a scene in this toolset. This distinguishes it from rename_scene, delete_scene, duplicate_scene, and fire_scene without naming them.

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 on when to create a scene versus using duplicate_scene, nor any prerequisites (e.g., whether the session must be in a particular view). The agent must infer usage entirely from the name.

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