Skip to main content
Glama

set_scene_name

Renames a scene in Ableton Live using its index and a new name, helping organize arrangement sections with clear labels.

Instructions

Rename a scene.

Parameters:

  • scene_index: The scene to rename

  • name: Its new name

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

Input Schema

NameRequiredDescriptionDefault
nameYes
scene_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and does not meet it: nothing about indexing base, whether renaming overwrites silently, what happens on an out-of-range index, or whether the change is reversible. Only the bare mutation intent is conveyed.

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?

One-line purpose followed by a compact parameter list; front-loaded and free of filler. The parameter list is redundant with the schema but does not bloat the definition.

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?

For a simple two-parameter mutation with an output schema available, the description is minimally adequate. The missing piece that matters most is the indexing convention for scene_index, which an agent cannot derive from a bare integer-typed schema.

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 description coverage is 0%, so the description must supply parameter meaning. It glosses both parameters, but "The scene to rename" and "Its new name" are near-tautological and omit critical details such as whether scene_index is zero-based or any constraints on the name string.

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?

"Rename a scene" states a specific verb and resource, and the resource (scene) is distinct from the sibling name-setters like set_clip_name and set_track_name. It does not explicitly contrast itself with those siblings, but the operation is unambiguous.

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 guidance on when to use this versus alternatives, and no mention of prerequisites such as the scene existing or how to obtain a valid scene_index. The agent must infer everything about invocation context.

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