Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_scene

Destructive

Deletes a scene row by its index in an Ableton Live Set, enabling removal of unwanted scenes during arrangement.

Instructions

Delete a scene row.

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

Input Schema

NameRequiredDescriptionDefault
indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — it does not say whether clips in the scene are also removed, whether the operation is undoable, or how the index behaves after deletion shifts the list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but it is terse to the point of under-specification for a destructive operation. Brevity here is not a virtue because essential context is omitted rather than compressed.

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?

An output schema exists, so return values need not be described, but the definition still leaves key gaps for a destructive tool: the meaning of the index and the fate of contained clips. Given the complexity of a DAW scene model, one sentence is insufficient.

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 single parameter "index" has 0% schema description coverage, so the description carries the full burden and fails to meet it. "Scene row" weakly implies the index is a scene position, but zero-based vs one-based numbering and bounds behavior are left unexplained.

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?

"Delete a scene row" names a specific verb (delete) and resource (scene), which separates it cleanly from create_scene, fire_scene, and set_scene_name in the sibling list. It does not, however, clarify how a scene row relates to the clips it contains, which matters for interpreting the action.

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?

There is no guidance on when to use this versus alternatives such as delete_clip or delete_track, and no prerequisites or warnings are stated. The agent must infer the use case entirely from the tool 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