Simpler.Asia

studio.shift_clips

Move 1 to 200 timeline clips by the same delta_ms (negative moves earlier), keeping their spacing and their tracks. All or nothing: an unknown clip id, a clip on a locked track, a clip pushed before 0 or past the timeline cap, or a landing that overlaps a clip you did not list refuses the whole call, names the first offending clip, and moves nothing; an overlap refusal gives the nearest delta_ms that fits. Scenes on the main track keep their order and are not clips; use reorder_scenes for them.

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>",
      "clip_ids": "<clip_ids>",
      "delta_ms": "<delta_ms>"
    },
    "name": "studio.shift_clips"
  }
}

Input Schema

Name	Required	Description
`clip_ids`	Yes	Timeline clip ids (vcl_) from get_composition's tracks; duplicates count once.
`delta_ms`	Yes	Milliseconds to move every listed clip; negative moves them earlier.
`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.6/5.0

Behavior5/5

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

Goes well beyond readOnlyHint=false: it discloses atomicity ("moves nothing"), enumerates the four refusal causes (unknown id, locked track, bounds breach, overlap with an unlisted clip), states that the first offending clip is named, and notes an overlap refusal returns a nearest-fitting delta_ms. That is precisely the failure-mode information an agent needs to plan retries.

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 range, then the atomicity contract, then the sibling exclusion — good ordering with no filler. The refusal sentence is long and clause-stacked, which costs a little readability.

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?

No output schema exists, and the description compensates by explaining what a refusal looks like and what a successful call preserves. Combined with a fully documented three-parameter schema, an agent has everything needed to call it and interpret failure correctly.

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 still adds meaning by framing delta_ms as a uniform shift that preserves relative spacing, which the schema's per-parameter text does not say. The negative-moves-earlier note and the 1–200 bound merely restate schema constraints.

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?

Names a specific verb and resource ("Move 1 to 200 timeline clips by the same delta_ms") and immediately states the scoping invariant — spacing and tracks preserved. It also distinguishes itself from reorder_scenes by declaring scenes are not clips, so an agent can separate this tool from its nearest sibling without opening a schema.

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 an explicit negative boundary ("Scenes on the main track ... are not clips; use reorder_scenes for them"), which is real routing guidance. It offers no guidance against other plausible alternatives such as move_clips_to_track, duplicate_clips, or slip_edit, so it stops short of full when/when-not coverage.

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?