Skip to main content
Glama

delete_scene

Deletes a scene and all clips in its row after user confirmation. Use it to remove unwanted scene slots and clear their clip content in Ableton Live.

Instructions

Remove a scene together with every clip in its row. Ask the user first.

Parameters:

  • scene_index: The scene to remove

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": {
      "scene_index": "<scene_index>"
    },
    "name": "delete_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that all clips in the row are destroyed and that user confirmation is required. It omits reversibility/undo behavior, whether the scene slot renumbers, and what happens if the index is invalid.

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, front-loaded sentences with zero filler, and the destructive scope is stated before the parameter note. The parameter block adds little, but nothing is wasted.

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?

An output schema exists, so return values need not be described, and the cascade effect is covered. For a destructive, unannotated mutation the definition is still thin on indexing conventions and irreversibility.

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?

Schema coverage is 0% for the single parameter, and the description only restates the name ("The scene to remove"). It does not say whether the index is 0- or 1-based or how to obtain a valid index, leaving the caller to guess.

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?

"Remove a scene together with every clip in its row" names a specific verb and resource and adds the cascade scope, which separates it from clip-level siblings like delete_clip. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Ask the user first" is a real usage precondition and the strongest guidance in the definition. However, there is no statement of when to choose this over delete_clip / delete_arrangement_clip, nor any precondition about scene existence or empty scenes.

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