Skip to main content
Glama

delete_scene

Remove a specific scene from Ableton Live, deleting all clips in that row.

Instructions

Delete a scene. All clips in that row are also removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scene_indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the key side effect that all clips in the scene row are removed, which is vital for understanding the tool's impact. It does not mention undoability or permissions, but for a simple delete operation, this is adequate.

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 two sentences, front-loaded with the purpose, and contains no unnecessary words. It is highly concise and efficiently conveys the essential information.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, output schema exists), the description covers the basic purpose and side effect. However, it lacks details like prerequisite that the scene must exist, whether the operation is reversible, or how the scene_index is interpreted. It is minimally adequate but not fully complete.

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

Parameters2/5

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

The only parameter, scene_index, has no description in the schema (0% coverage). The tool description does not add any meaning beyond the schema, such as explaining how to obtain the index (e.g., zero-based) or its relationship to the scene list. This lacks helpful guidance for the agent.

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 clearly states 'Delete a scene' and explicitly mentions the cascading effect of removing all clips in that row. This distinguishes it from sibling tools like delete_clip (which deletes a single clip) and delete_track, providing a specific verb-resource pair.

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?

The description implies when to use the tool (when you want to remove a scene and its clips) but does not explicitly state when not to use it or provide alternatives. Given the sibling tools, an agent can infer the appropriate context, but no direct guidance is given.

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

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