Simpler.Asia

studio.reorder_scenes

Move a scene to a different position in the primary lane. Positions are 0-based, so to_index 0 makes it the opening scene. Scene start times are DERIVED from order, so every scene after the move shifts in time. With ripple_secondary "shift" (the default) every clip, caption and sticker that sits wholly inside a scene moves with that scene; one that spans a scene edge stays put and is listed in straddling_ids. "none" moves the scenes alone. Refuses a shift that moves a clip on a locked track (unlock it with lock_track, or pass ripple_secondary "none") or lands a moved clip over one that stays put (pass ripple_secondary "none", or move or split that clip first).

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>",
      "scene_id": "<scene_id>",
      "to_index": "<to_index>"
    },
    "name": "studio.reorder_scenes"
  }
}

Input Schema

Name	Required	Description	Default
`scene_id`	Yes
`to_index`	Yes	0-based destination position.
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`ripple_secondary`	No	"shift" (default) keeps clips, captions and stickers in sync with the scenes; "none" edits the main track alone.	shift

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With only readOnlyHint=false available, the description carries the behavioral burden and does so thoroughly: it discloses derived start times, ripple effects on clips/captions/stickers, straddling behavior and straddling_ids, and precise refusal conditions for locked tracks and collisions. This is exactly the kind of mutation context an agent needs.

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 description is front-loaded with the core action and then layers ripple semantics and refusal conditions in a logical order. It is dense and appropriately sized for a complex mutation, though the long final sentence could be split for easier scanning.

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?

There is no output schema, but the description mentions straddling_ids and the refusal behavior, covering the most important return/error signals. It does not describe the full return shape or any authorization requirements, leaving minor gaps for a complex mutation tool.

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 75%, and the description still adds substantial meaning: to_index is explained as 0-based with a concrete example, and ripple_secondary is explained in terms of scene-contained vs scene-straddling elements. The project_id and scene_id parameters rely on the schema and their names, but the description compensates well for the highest-risk parameter.

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?

The description opens with a specific verb and resource: "Move a scene to a different position in the primary lane." It names the scope (primary lane), the positional semantics (0-based), and the derived-time consequence, so an agent can distinguish this from sibling tools like update_scene, trim_scene, or move_track.

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?

It gives clear conditional guidance for ripple_secondary: "shift" (default) moves contained clips/captions/stickers with the scene, while "none" moves scenes alone. It also explains refusal conditions and prescribes remediation via lock_track or ripple_secondary "none". It stops short of explicitly routing the agent to alternative sibling tools for broader timeline restructuring.

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?