Skip to main content
Glama

range_remove

Remove all content between a start and end time on selected or all unlocked tracks, cutting clips at both edges and optionally closing the gap with a ripple delete.

Instructions

Remove everything between start and end on the given tracks (default: all unlocked video+audio tracks): clips are cut at both edges and the middle deleted. ripple=true closes the gap (like a ripple delete).

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "range_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
rippleNo
tracksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does well on the core mechanics — destructive removal of a middle segment, edge cutting, and exactly what ripple=true does — but says nothing about irreversibility, undo behavior, what happens when start/end span a clip boundary, or behavior on locked tracks.

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?

Two tight sentences with the destructive core front-loaded and the ripple semantics trailing as a qualifier. The colon-separated mechanics clause is slightly dense but every clause carries information; nothing is 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, annotation-free, four-parameter tool with no output schema, the description explains the edit model but omits the time-unit convention for start/end and any statement of what the call returns or how it fails. Adequate to attempt a call, not adequate to call it confidently.

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 0%, so the description must compensate for four parameters. It covers tracks (default all unlocked video+audio) and ripple (default true, closes the gap), but leaves start/end as bare names with no unit or format (timecode, seconds, frames) and does not clarify whether the range is inclusive or exclusive.

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 ("Remove everything between start and end on the given tracks") and immediately clarifies the mechanics: edges are cut, the middle deleted. An agent can distinguish this from a trim or a whole-clip delete without opening the schema, though no sibling is named by way of contrast.

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?

The default scope ("all unlocked video+audio tracks") implies when the tool applies at a broad level, but there is no explicit guidance on when to prefer this over clip_trim or clips_delete, nor any stated prerequisite such as an unlocked/editable track or a valid playhead range.

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