Skip to main content
Glama

filmcraft_ripple_delete

Deletes selected timeline clips or empty gaps and shifts subsequent media left to close the resulting space.

Instructions

Deletes selected clips or empty gaps on the timeline, automatically shifting subsequent media left to close the gap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "filmcraft_ripple_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdsNoArray of clip IDs to ripple delete
gapRangeNoSpecific gap range to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral burden. It does disclose the critical side effect — subsequent media shifts left to close the gap — which is the main non-obvious trait of a ripple operation, but it omits reversibility/undo, cross-track sync impact, and error behavior for a destructive mutation.

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?

A single front-loaded sentence that states the action, the targets, and the consequence with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive timeline mutation with no annotations and no output schema, the description covers the core ripple semantics but leaves gaps: no return value, no statement about undo, and no clarification of the clips-vs-gapRange relationship for two optional parameters.

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 description coverage is 100%, so both clipIds and gapRange are already documented structurally. The description hints at a two-mode model (clips vs. gaps) but never says whether the parameters are mutually exclusive or what happens if neither/both are supplied, so it adds only marginal meaning.

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 (deletes) and specific resources (selected clips or empty gaps on the timeline), plus the resulting behavior. An agent can distinguish this from razor_cut or slip_slide, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the operation described (removing content and closing the gap), but there is no guidance on when to prefer this over razor_cut or slip_slide, nor any note about prerequisites such as selection state or locked tracks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.