Skip to main content
Glama

set_clip_name

Rename clips in Ableton Live tracks by specifying track and clip indices with a new name for music production organization.

Instructions

Set the name of a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • name: The new name for the clip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
clip_indexYes
nameYes

Implementation Reference

  • The implementation of the set_clip_name tool logic in the Ableton Remote Script.
    def _set_clip_name(self, track_index, clip_index, name):
        """Set the name of a clip"""
        try:
            if track_index < 0 or track_index >= len(self._song.tracks):
                raise IndexError("Track index out of range")
            
            track = self._song.tracks[track_index]
            
            if clip_index < 0 or clip_index >= len(track.clip_slots):
                raise IndexError("Clip index out of range")
            
            clip_slot = track.clip_slots[clip_index]
            
            if not clip_slot.has_clip:
                raise Exception("No clip in slot")
            
            clip = clip_slot.clip
            clip.name = name
            
            result = {
                "name": clip.name
            }
            return result
        except Exception as e:
            self.log_message("Error setting clip name: " + str(e))
            raise
  • The MCP tool handler definition in the MCP server.
    def set_clip_name(ctx: Context, track_index: int, clip_index: int, name: str) -> str:
        """
        Set the name of a clip.
    
        Parameters:
        - track_index: The index of the track containing the clip
        - clip_index: The index of the clip slot containing the clip
        - name: The new name for the clip
        """
        try:
            _run("set_clip_name", {
                "track_index": track_index,
                "clip_index": clip_index,
                "name": name
            })
            return f"Renamed clip at track {track_index}, slot {clip_index} to '{name}'"
        except Exception as e:
            return f"Error setting clip name: {e}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool sets a clip's name, implying a mutation operation, but fails to describe any behavioral traits such as permission requirements, whether the change is reversible, error conditions (e.g., invalid indices), or side effects. This leaves significant gaps 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.

Conciseness4/5

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

The description is appropriately sized and front-loaded, starting with the core purpose followed by parameter details. Every sentence earns its place by clarifying the tool's function and inputs, though the parameter section could be more integrated into the flow rather than listed separately.

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 the tool's mutation nature, lack of annotations, no output schema, and low schema coverage, the description is insufficiently complete. It doesn't address behavioral risks, error handling, or output expectations, leaving the agent poorly equipped to use this tool correctly in a production context.

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

Parameters3/5

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

The description lists all three parameters with brief explanations, adding meaning beyond the input schema, which has 0% description coverage. However, it doesn't provide crucial details like valid ranges for indices, name length limits, or formatting rules. This partially compensates for the schema gap but remains incomplete for safe invocation.

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 tool's purpose with a specific verb ('Set') and resource ('the name of a clip'), making it immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'set_track_name' or 'create_clip', which would require mentioning it specifically modifies existing clips rather than tracks or creating new ones.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing clip), exclusions, or comparisons to siblings like 'set_track_name' for track naming or 'create_clip' for new clips, leaving the agent to infer usage context from the tool name alone.

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