Create a new scene in Ableton Live 12 at a chosen index or append it to the end of the set.
Creates a new scene in Ableton Live 12 (Song.create_scene).
| Name | Required | Description | Default |
|---|---|---|---|
| index | No | Zero-based index at which to insert the scene, or -1 to append at the end. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only names the action; it does not say whether the new scene is empty, where clips from an existing scene go, whether the operation is undoable, or what the result contains. Mentioning Song.create_scene is a small traceability aid but not behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence with the action front-loaded and no filler. It is efficient, though slightly under-specified for a mutation tool rather than genuinely tight writing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-optional-parameter creation tool with a fully described schema and no annotations, the description is minimally adequate. It omits what creation returns (e.g., new scene index) and has no output schema to fall back on, leaving a gap an agent would notice after the call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single 'index' parameter documents both the zero-based insertion point and the -1 default, so the description need not repeat it. Baseline 3 applies; the description adds nothing to parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Creates a new scene in Ableton Live 12') plus the underlying LOM call, which is unambiguous. It does not, however, distinguish itself from sibling tools like live12_scene_fire or live12_scene_set_properties, which operate on existing scenes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to create a new scene versus firing or modifying an existing one, and no prerequisites or side-effect warnings are given. The agent must infer that this is the only tool that adds a scene.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.