Simpler.Asia

studio.delete_elements

Delete several scenes, timeline clips, stickers and captions in one edit: pass 1 to 200 ids in element_ids. All or nothing: an unknown id, a clip on a locked track, or a locked track a scene's cut would move refuses the whole call, names the first offender, and deletes nothing (unlock it with lock_track, or pass ripple_secondary "none"). Scenes follow ripple_secondary as in delete_element: "shift" (default) removes each deleted scene's time from every lane, keeping later clips in sync; "none" closes the main track alone. The receipt's clips_removed and clips_trimmed count each unlisted clip once, however many deleted scenes it spanned. Listed clips leave gaps (ripple_delete closes one); captions hide reversibly (restore_fillers brings them back).

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_ids": "<element_ids>"
    },
    "name": "studio.delete_elements"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes	The studio project (vp_…) this tool acts on.
`element_ids`	Yes	Scene (vs_), clip (vcl_), sticker (vov_) or caption (vc_) ids; duplicates count once.
`ripple_secondary`	No	For deleted scenes: "shift" (default) removes their time from every lane; "none" closes the main track alone. Clips, stickers and captions ignore it.

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?

With only readOnlyHint=false available, the description carries the full behavioral burden and does so strongly. It discloses atomic all-or-nothing semantics, specific refusal conditions, ripple behavior, receipt counting rules, gap behavior for clips, and reversible caption hiding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded and every sentence contributes operational meaning. The atomicity constraint, ripple_secondary behavior, and sibling alternatives are presented in a logical order without 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 mutation tool with no output schema, the description is complete enough to call correctly: it explains accepted inputs, failure behavior, ripple semantics, and receipt fields. No critical decision information 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 already 100%, but the description still adds meaningful semantics beyond the schema, especially for ripple_secondary: default behavior, effect on lanes, and how scenes versus clips/stickers/captions use it. Some element_ids detail repeats the schema's accepted types and duplicate handling.

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 gives a specific verb and resource set: deleting several scenes, timeline clips, stickers, and captions in one edit. It clearly distinguishes the batch operation from the singular sibling studio.delete_element and from ripple_delete.

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 states when to use this tool, gives the 1–200 element_ids range, and explicitly names alternatives for related needs: lock_track for locked tracks, ripple_delete for closing gaps left by listed clips, and restore_fillers for reversing caption hiding.

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?