Simpler.Asia

studio.trim_scene

Trim a generated scene's footage: cut milliseconds off its start and/or end. With ripple_secondary "shift" (the default) the other lanes follow the footage: time the scene loses at its start or end is cut from every lane at that edge, and time it gains is inserted there, so clips, captions and stickers stay over the frames they were placed on (one that spans that edge is split or stretched). "none" changes the main track alone. Refuses a shift that moves a locked track (unlock it with lock_track, or pass ripple_secondary "none").

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>"
    },
    "name": "studio.trim_scene"
  }
}

Input Schema

Name	Required	Description	Default
`scene_id`	Yes
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`trim_end_ms`	No	Milliseconds to cut from the end.
`trim_start_ms`	No	Milliseconds to cut from the start.
`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.1/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 load well: it discloses that secondary lanes shift, that spanning clips are split or stretched, and that the operation refuses when a locked track would move. These are non-obvious side effects and failure modes an agent needs before invoking a mutation.

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 core action, then the ripple semantics, then the refusal case. The final sentence is slightly tangled but conveys an actionable prerequisite; no filler sentences.

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 5-parameter mutation with no output schema, the description covers side effects, edge-case splitting behavior, and the locked-track failure mode. Return values are not described, but that is a minor gap given the behavioral coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema already documents project_id, trim_start_ms, trim_end_ms, and ripple_secondary. The description's explanation of ripple_secondary largely restates the schema text and adds no format or unit details beyond it; baseline 3 applies.

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 with scope: trims a generated scene's footage by cutting milliseconds from start and/or end. That clearly separates it from generic clip editing, though it never names close siblings like studio.trim_clip or studio.cut_range, so the agent must infer the distinction.

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?

Explains when ripple_secondary "shift" applies (default, moves every lane) versus "none" (main track alone), and gives a concrete remediation path when a locked track blocks the shift: unlock via lock_track or pass "none". It lacks explicit routing guidance against sibling trimming tools.

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?