Skip to main content
Glama

set_track_name

Rename any Ableton Live track by index to assign clear labels, keeping arrangements organized and easier to navigate during mixing.

Instructions

Rename a track.

Parameters:

  • track_index: The track 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": {
      "track_index": "<track_index>",
      "name": "<name>"
    },
    "name": "set_track_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
track_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, the description carries the full burden of behavioral disclosure and does not meet it. 'Rename' implies mutation and destruction of the prior name, but nothing is said about whether the change is immediate, persistable, undoable, or what happens with an invalid track_index.

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 core action is front-loaded in one sentence and the short parameter list adds no padding. It is efficient, though the parameter lines are near-verbatim restatements rather than value-adding notes.

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?

An output schema exists, so return values need not be explained, and the tool is a simple two-parameter mutation. However, for a state-changing operation with zero annotation coverage, the missing index semantics and mutation behavior leave real gaps.

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 compensate, but it only restates parameter titles ('track_index: The track to rename', 'name: Its new name'). It omits critical semantics such as whether the index is zero-based or how to obtain a valid index.

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?

States a specific verb and resource ('Rename a track'), which clearly separates it from sibling name-setters like set_clip_name and set_scene_name by scope. It does not explicitly name those siblings, but the resource noun does the disambiguation work.

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 tool versus alternatives, no preconditions (e.g., requiring a valid track index from get_track_info), and no note about overwriting an existing name. The reader must infer all usage 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