Skip to main content
Glama

delete_clips

Destructive

Remove specified clips from the DaVinci Resolve media pool while leaving the original media files on disk untouched.

Instructions

Delete clips from the media pool (media on disk is untouched).

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": "delete_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context by stating the blast radius: media on disk is untouched, meaning only the pool entry is removed. It stops short of saying whether the removal is reversible or undoable, which keeps it from a 5.

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?

One short sentence with the scope qualifier attached directly to the action, and no filler. Every clause carries information the agent cannot get from the schema or annotations alone.

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 single-parameter destructive tool with no output schema, the description covers purpose and blast radius but leaves the identifier format and post-delete response undefined. It is adequate to avoid a wrong-target deletion on disk, but not complete enough to call the tool confidently without inspecting the data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the schema supplies only the name and array-of-string type. The description does not say whether entries are clip IDs, names, or paths, nor how multiple clips are handled. With one undocumented parameter, the description needed to compensate and does not.

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 ("Delete clips") and narrows the scope with "from the media pool", which distinguishes it from deleting files on disk. It does not, however, distinguish itself from nearby siblings such as delete_items or delete_bins, so the agent must infer which collection a clip belongs to.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative for removing timeline items versus media pool entries. The only guidance is the implied scope in the parenthetical, which tells the agent what is unaffected rather than when to pick this tool.

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

Deploy Server

Other Tools