Simpler.Asia

studio.slide_edit

Move a video or audio clip by delta_ms between its neighbours on its track: the clip touching its start gets longer or shorter at its end, the clip touching its end at its start, so the three-clip span and every other track stay put. A side with a gap instead lets the clip move into the gap and no further. Refuses, naming the fix: an unknown id, a scene (scenes reorder with reorder_scenes), text or a still image (move it with shift_clips), a locked track, or a delta that would leave a neighbour under 100ms or past its footage (the refusal gives the delta_ms range that fits).

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_id": "<clip_id>",
      "delta_ms": "<delta_ms>"
    },
    "name": "studio.slide_edit"
  }
}

Input Schema

Name	Required	Description
`clip_id`	Yes	A video or audio clip (vcl_) on a secondary track.
`delta_ms`	Yes	Milliseconds to move the clip; negative moves it 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.8/5.0

Behavior5/5

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

Annotations only supply readOnlyHint=false, so the description carries the load and does so well: it discloses that neighbours absorb the delta, that gaps cap the movement, that the overall three-clip span and other tracks are invariant, and that refusals come back with a valid delta_ms range. That is exactly the behavioural context an agent needs before a mutating edit.

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 core action is front-loaded in the first clause and every subsequent sentence adds a distinct constraint or refusal case. It is dense and reads as one long block, which slightly hurts scanability, but there is no filler.

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?

For a 3-parameter mutation tool with no output schema, the description covers preconditions, side effects, invariants and failure modes. Nothing an agent needs to invoke 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 the baseline is 3; the description earns above that by explaining that delta_ms is relative to neighbours, that negative means earlier, and that clip_id must be a video or audio clip on a secondary track. It stops short of documenting units/limits beyond what the schema already states.

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 pairs a specific verb (move) with the resource (video/audio clip) and the exact quantity (delta_ms), then spells out the neighbour-stretch semantics that make this tool distinct. It is clearly separable from shift_clips, roll_edit, slip_edit and reorder_scenes.

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?

It explicitly routes the agent elsewhere: scenes go to reorder_scenes, text and still images go to shift_clips, and gap-side behaviour is defined. The refusal list names each precondition (unknown id, locked track, 100ms floor, footage bound) along with the fix, which is stronger than mere when-to-use guidance.

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?