Skip to main content
Glama

Simpler.Asia

studio.move_clips_to_track

Move 1 to 200 timeline clips onto another track of the same kind (a b-roll clip to a video-broll track, a title to a text track, music to an audio-music track, a voice clip to an audio-voice track), keeping their spacing; delta_ms also moves them in time (default 0). Stacking follows the track: get_composition lists tracks in stacking order, and a clip on a later video-broll or text track draws over the earlier ones. All or nothing. Refuses, naming the first offender and moving nothing: an unknown clip id or track_id (get_composition lists the ids), a locked source or target track (unlock it with lock_track), a target of another kind (pick a track of the clip's kind, or add one with add_track), a target that would pass its clip cap (move fewer clips, or add a track with add_track), listed clips that overlap each other (move them one at a time), a clip pushed before 0 or past the timeline cap (keep delta_ms within the range the refusal gives), or a landing that overlaps a clip already on the target (use another delta_ms; the refusal gives the nearest one that fits).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clip_idsYesTimeline clip ids (vcl_) from get_composition's tracks; duplicates count once.
delta_msNoMilliseconds to move the clips in time as they change track; negative moves them earlier. 0 when left out.
track_idYesThe target track (vtr_) from get_composition's tracks, of the same role as every listed clip's track.
project_idYesThe studio project (vp_…) this tool acts on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the load and does it well: atomic all-or-nothing semantics, refusal naming the first offender with nothing moved, stacking/draw-order behavior, clip caps, and timeline bounds. This is exactly the mutation context an agent needs before calling.

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?

Front-loaded with the action and constraint, then a single enumerated refusal list where each clause earns its place by pairing a cause with a remedy. It is dense and long for one paragraph, but there is almost no filler to cut.

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

Completeness5/5

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

With no annotations beyond readOnlyHint=false and no output schema, the description supplies the full behavioral contract — atomicity, ordering, bounds, and per-error remediation. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds real semantics: the 1–200 clip count, delta_ms default of 0 and its interaction with the 0 and timeline-cap bounds, and that track_id must be the same role as every clip's track. Only the refusal-range hint ('the range the refusal gives') is vague.

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 ('Move 1 to 200 timeline clips onto another track of the same kind') plus the kind-matching constraint and delta_ms side effect. Clearly separable from siblings like studio.move_track (tracks, not clips), studio.shift_clips, and studio.duplicate_clips.

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

Usage Guidelines5/5

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

Explicitly routes the agent to get_composition for ids, lock_track to unlock, add_track when no valid or uncapped target exists, and 'move them one at a time' when listed clips overlap. It effectively provides when-and-how alternatives for every failure path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources