Skip to main content
Glama

set_arrangement_clip_name

Rename an Arrangement clip by specifying its track index, clip index, and new name.

Instructions

Rename a clip in the Arrangement.

Parameters:

  • track_index: The track

  • clip_index: Position of the clip in get_arrangement_clips (ordered by start time)

  • 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_arrangement_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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden; it does disclose the real mechanic that clip_index is positional and ordered by start time in get_arrangement_clips, which is genuinely useful. It omits what happens on out-of-range indices, whether the clip must exist, and whether the operation is reversible or idempotent.

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 purpose sentence is front-loaded and the parameter list is compact with no filler. The only weakness is that "name: Its new name" restates the field title without adding meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with an output schema present, the description covers purpose, all parameters, and the prerequisite lookup for clip indexing. Missing failure-mode details are minor given the tool's low complexity and the separate output schema.

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?

Schema description coverage is 0% and all three properties are bare titles, so the description must compensate; it does well for clip_index (positional, ordered by start time per get_arrangement_clips) and name (the new name), but track_index is only glossed as "The track" with no indexing base or resolution hint.

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 clip") plus an explicit scope ("in the Arrangement"), which distinguishes it from the sibling set_clip_name that operates elsewhere. A sibling name alone is not enough to fully differentiate, but the Arrangement scoping is stated in the description itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the agent can infer it should first call get_arrangement_clips because clip_index is defined relative to that output. There is no explicit when-to-use/when-not guidance or named alternative for non-Arrangement clips, so the agent must infer the boundary.

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