Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Delete clips

delete_clip
Destructive

[write] Remove clips, leaving a gap (ripple_delete_clip closes it). Use to drop a clip where the gap should stay. Not for closing the gap (use ripple_delete_clip or close_gap) or removing a motion graphic and every clip of it (use delete_asset). Returns the changed clips' rows (with handles) and counts. Related: ripple_delete_clip, close_gap, get_timeline. Full docs: load_skill with tools: [name].

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>"
    },
    "name": "delete_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoget_timeline handle.
idsNoHandles, instead of id.
itemsNoMany clips at once, max 60, each with this tool's fields.
project_idYesThe AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is structured data. The description adds real value beyond that by stating the timeline side effect (a gap is left) and the return payload (changed clip rows with handles, plus counts), which matters since no output schema exists. It does not cover permissions, whether deletions are undoable, or partial-failure behavior when multiple ids are passed.

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 write marker and the core semantic, and every sentence carries routing or behavior information. The trailing "Full docs: load_skill" pointer is a small amount of boilerplate but is plausibly useful for deeper usage.

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 destructive mutation with no output schema, the description supplies the consequence, the return shape, and sibling routing, which covers what an agent needs to invoke it. The remaining gap is failure/undo semantics and how ids/items interact on batch deletes.

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%, with each of id, ids, items, and project_id documented in-schema. The description adds no parameter-level detail such as precedence between id/ids/items or the 60-item cap, so the baseline of 3 applies — the schema does all the work.

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 ("Remove clips") plus the defining consequence — leaves a gap rather than closing it. It explicitly distinguishes itself from ripple_delete_clip, close_gap, and delete_asset, so an agent can pick it without opening any schema.

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?

Gives a positive rule ("Use to drop a clip where the gap should stay") and two explicit when-not rules with named alternatives for each case. The routing decision is fully resolved in the description text.

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

All AskEditor toolsInspect
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