Skip to main content
Glama
Sign In

Simpler.Asia

by asia.simpler
OverviewDiscussionsAdmin

studio.move_track

Move a track to position within its own role. Position 0 is the lowest: its pictures draw first, so every later video-broll or text track draws over it. Tracks of other roles keep their order; text always draws over video. Locked tracks may be reordered. Refuses an unknown track_id or a position past the role's last track, 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>",
      "position": "<position>"
    },
    "name": "studio.move_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYes0-based position among the tracks of the same role; 0 draws lowest.
track_idYesThe track (vtr_) from get_composition's tracks.
project_idYesThe studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the readOnlyHint=false annotation by disclosing edge-case behavior: locked tracks may be reordered, and the tool refuses an unknown track_id or out-of-range position while naming the fix. It does not say whether the move is undoable or what happens to clips sitting on the track, which would complete the mutation picture.

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 tight sentences, front-loaded with the action, then ordering semantics, then failure behavior. No filler and no repetition of the schema's field docs.

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-parameter mutation tool with no output schema and only a readOnlyHint annotation, the description covers ordering semantics, role isolation, and error conditions well. Missing are reversibility/undo and the post-move state, which matter for a destructive-ish reorder operation.

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?

Schema coverage is 100%, so the baseline is 3; the description earns one extra by explaining the consequence of the position value — 0 draws first and later tracks composite over it — which the schema only states tersely as '0 draws lowest'. It adds z-order reasoning rather than restating the field definitions.

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 ('Move a track') plus the key scoping constraint ('within its own role'), which separates it from a global reorder. It never names the adjacent tools (studio.move_clips_to_track, studio.reorder_scenes, studio.move_caption), so sibling differentiation is left to inference.

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?

The description gives clear operating context: position is role-relative, other roles keep their order, and locked tracks are still reorderable. It stops short of explicit when-to-use routing against alternatives, so the agent must infer that this tool moves tracks rather than clips or scenes.

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

All Simpler.Asia toolsInspect
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