Simpler.Asia

studio.rename_track

Give a track a display name up to 40 characters, or pass an empty name to go back to the role's label. Names are for people and never address a track: tools take track_id. Locked tracks may be renamed. Refuses an unknown track_id, naming the fix.

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": {
      "project_id": "<project_id>",
      "track_id": "<track_id>",
      "name": "<name>"
    },
    "name": "studio.rename_track"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The new name; an empty string clears it.
`track_id`	Yes	The track (vtr_) from get_composition's tracks.
`project_id`	Yes	The studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds real behavior beyond readOnlyHint=false: locked tracks may still be renamed (a non-obvious permission), the 40-character ceiling, the empty-string reset semantics, and the failure mode of refusing an unknown track_id while naming the fix. These are exactly the surprises an agent needs before mutating state.

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?

Three short sentences, front-loaded with the primary action and the reset case, followed by the disambiguation and the error contract. Every clause carries information; nothing is filler.

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 3-required-parameter mutation with only readOnlyHint=false and no output schema, the description covers scope, reset semantics, permissions on locked tracks, and the error path. The only unstated piece is what the tool returns after a successful rename, which is minor since no output schema exists either.

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 coverage is 100% and each field already documents itself, including maxLength 40 and 'an empty string clears it' on name. The description restates those same facts rather than adding new syntax or format guidance, so it meets but does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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) plus the reversible variant (empty name restores the role label). The line 'Names are for people and never address a track: tools take track_id' cleanly separates renaming from the addressing-style siblings like studio.move_track or studio.set_track_muted.

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

Usage Guidelines4/5

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

Gives a clear when-to-use rule (display naming, not addressing) and a when-to-do-the-inverse rule (empty string clears). It does not name an explicit alternative tool for renaming, and there is no exclusion for e.g. role changes, so it stops short of full alternative routing.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?