Skip to main content
Glama

set_clip_name

Rename a Session clip in Ableton Live by setting its track index, clip index, and new name.

Instructions

Rename a Session clip.

Parameters:

  • track_index: The track

  • clip_index: The Session slot

  • 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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "name": "<name>"
    },
    "name": "set_clip_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it. Nothing is said about failure modes on an invalid index, whether renaming overwrites an existing name, name length constraints, or whether the change is undoable — all relevant for a mutation tool.

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 description is short and front-loads the action, which is good. However, the parameter block consumes most of the text while conveying almost no information, so space is allocated without earning value.

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 for a three-parameter mutation with zero schema coverage and no annotations, the definition omits index conventions, error behavior, and any usage context — leaving real gaps for a simple tool.

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 define the three parameters, but it only restates their names: "The track", "The Session slot", "Its new name". It never states whether indices are zero-based or relative to the visible track list, which is the one piece of meaning an agent actually needs here.

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 Session clip" gives a specific verb (rename) and resource (Session clip), and the qualifier "Session" implicitly separates it from the arrangement-clip sibling. It stops short of naming that alternative explicitly, 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?

There is no when-to-use guidance, no statement of prerequisites (must the clip already exist?), and no reference to alternatives such as the arrangement-clip naming tool. The agent must infer the selection context 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