Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by rephlex187
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_scene

Delete a scene from an Ableton Live session by specifying its index. Removes the scene and its clips.

Instructions

Delete the scene at the given index.

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

Input Schema

NameRequiredDescriptionDefault
ctxYes
scene_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'delete' but does not disclose irreversible nature, effect on contained clips, or any side effects. Minimal 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.

Conciseness4/5

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

Single sentence is very concise, but no additional structure or separation of concerns. Every word earns its place, but lacks any breakdown of parameters or behavior.

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?

Simple tool with no output schema and no annotations. Description is insufficient: does not explain return value, error cases, or prerequisites. Agent would need to infer safe usage.

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 has 0% description coverage for parameters. The description mentions 'at the given index' but does not specify zero- or one-based indexing. The required 'ctx' parameter is not explained at all.

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?

Description explicitly states the action 'delete' and resource 'scene at the given index'. It is a specific verb+resource pair that clearly distinguishes from siblings like 'duplicate_scene', 'fire_scene', etc.

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?

No explicit guidance on when to use this tool vs alternatives. The description implies use when deletion is desired, but lacks context on prerequisites (e.g., scene must exist, cannot delete last scene) or when not to use.

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