Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by rephlex187
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_scenes

Retrieve all scene names from the current Ableton Live session to view the session structure and organize clips.

Instructions

List all scenes in the session.

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>"
    },
    "name": "list_scenes"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states a basic list operation. It does not reveal whether it is read-only, any permissions needed, or what happens when there are no scenes.

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?

The description is a single, efficient sentence with no unnecessary words. It is front-loaded with the core action, but could benefit from slightly more detail without losing conciseness.

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?

Given no output schema and no annotations, the description is too minimal. It does not specify the return format, whether results are paginated, or any other behavioral details needed for full agent comprehension.

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 'ctx' is a complex Context object, but the description does not explain its role or usage. Schema description coverage is 0% for the parameter, and the description fails to compensate by clarifying how to use the context.

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 the verb 'list', the resource 'scenes', and the scope 'in the session'. It effectively distinguishes from sibling tools like create_scene, delete_scene, and get_scene_info.

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?

No guidelines are provided about when to use this tool versus alternatives like get_scene_info or list_tracks. There is no mention of prerequisites or context, leaving the agent without guidance on selection.

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