Simpler.Asia

studio.ripple_delete

Delete a scene or timeline clip AND close the time it held. scope "all_tracks" (the default) removes that span of time from every lane, so everything after it moves earlier together and stays in sync; clips and captions over the span go with it, and one that crosses its edge is split or shortened. scope "own_track" closes the gap on the element's own lane only (for a scene, the other tracks then drift by its length). delete_element and delete_elements leave a clip's gap open instead. Refuses, naming the fix: an unknown id, a sticker or caption (no lane time to close), a locked track the edit moves, or with all_tracks a clip that runs past the main track's end.

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

Input Schema

Name	Required	Description
`scope`	No	"all_tracks" (default) closes the time on every lane; "own_track" closes it on the element's own lane only.
`element_id`	Yes	A scene (vs_) or timeline clip (vcl_) id from get_composition.
`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.9/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 full burden and does it well: it discloses downstream rippling, splitting/shortening of crossing clips, caption loss, and the other-tracks drift for own_track scenes. It also enumerates the refusal cases with the fix implied, which is exactly the pre-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?

Front-loaded with the core action and side effect, then scope semantics, then refusals. It is a dense paragraph with no filler, though the long chained clauses make it slightly heavier to parse than necessary.

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 destructive edit tool with no output schema, it covers what is destroyed, what is preserved, how neighboring clips are affected under each mode, and the exact conditions under which the call is rejected. Nothing material is missing.

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

Parameters5/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 goes beyond the schema by explaining the consequences of each enum value (all_tracks moves everything earlier and stays in sync; own_track causes other tracks to drift by the element's length) and confirming all_tracks is the default.

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 (delete a scene or timeline clip) plus the non-obvious side effect (closes the time it held). It immediately differentiates from delete_element/delete_elements by naming the gap-closing behavior those tools lack.

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 names the two sibling alternatives and the behavioral difference: 'delete_element and delete_elements leave a clip's gap open instead.' It also states the scope choice criteria (ripple everything vs. own lane) rather than leaving the agent to infer.

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?