Skip to main content
Glama

clips_delete

Delete timeline clips by reference, ID, selection, or track; enable ripple to close gaps and control linked audio/video removal.

Instructions

Delete timeline clips (refs, ids, 'selected' or a whole track 'V2'). ripple=true closes the gap. Linked audio/video is deleted too unless with_linked=false.

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": {
      "clips": "<clips>"
    },
    "name": "clips_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
rippleNo
with_linkedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two important behavioral traits: ripple=true closes the resulting gap, and linked audio/video is removed too unless with_linked=false — a meaningful consequence most callers would miss. It is silent on irreversibility/undo, whether deletion is immediate, confirmation requirements, and what the tool returns.

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?

Two tightly written sentences, front-loaded with the operation and accepted inputs, followed by the two behavioral flags. No filler or restated title.

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 three-parameter destructive tool with no annotations and no output schema, this covers inputs and side effects well. The remaining gap is post-call behavior — what is returned or how to confirm/undo the deletion.

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 description coverage is 0%, so the description must compensate, and it does so for all three parameters: acceptable clips values, the gap-closing effect of ripple, and the linked-media side effect governed by with_linked. It stops short of stating the schema defaults (ripple=false, with_linked=true) explicitly or the exact reference/id syntax.

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 (delete) and resource (timeline clips), and enumerates the accepted ways to identify them (refs, ids, 'selected', or a track like 'V2'). The destructive delete verb clearly separates it from neighboring tools such as clips_place, clips_link, and clips_assemble.

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 description tells the agent what can be passed for the clips argument, including the 'selected' shortcut, which implies the common usage path. However, it offers no explicit when-to-use vs when-not guidance, no prerequisites, and does not state whether an undo path exists.

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