Skip to main content
Glama

set_track_name

Rename tracks in Ableton Live sessions by specifying track index and new name to organize your music production workflow.

Instructions

Set the name of a track.

Parameters:

  • track_index: The index of the track to rename

  • name: The new name for the track

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
nameYes

Implementation Reference

  • The actual implementation in the Ableton Remote Script that renames the track.
    def _set_track_name(self, track_index, name):
        """Set the name of a track"""
        try:
            if track_index < 0 or track_index >= len(self._song.tracks):
                raise IndexError("Track index out of range")
            
            # Set the name
            track = self._song.tracks[track_index]
            track.name = name
            
            result = {
                "name": track.name
            }
            return result
        except Exception as e:
            self.log_message("Error setting track name: " + str(e))
  • The MCP tool handler function definition.
    def set_track_name(ctx: Context, track_index: int, name: str) -> str:
        """
        Set the name of a track.
    
        Parameters:
        - track_index: The index of the track to rename
        - name: The new name for the track
        """
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Set' implies a mutation, it doesn't specify permissions needed, whether the change is reversible, error conditions (e.g., invalid track_index), or what happens on success. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is extremely concise with zero wasted words. It uses a clear heading structure with bullet points for parameters, making it easy to parse. Every sentence earns its place.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after execution (success response, error conditions), nor does it provide context about track_index constraints (e.g., valid range, zero-based indexing). The parameter explanations help but don't cover behavioral aspects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explicitly lists both parameters with brief explanations ('The index of the track to rename', 'The new name for the track'), adding meaningful context beyond the schema which has 0% description coverage. This fully compensates for the schema's lack of parameter descriptions.

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?

The description clearly states the action ('Set') and resource ('name of a track'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'set_clip_name' which performs a similar renaming operation on a different resource type.

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 is provided about when to use this tool versus alternatives like 'set_clip_name' or whether there are prerequisites (e.g., track must exist). The description only states what the tool does, not when it should be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FreeRiverHouse/ableton-flow'

If you have feedback or need assistance with the MCP directory API, please join our Discord server