Skip to main content
Glama
Sign In
resolve-mcp

resolve-mcp

by irstone-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clip_delete

Removes clips from the DaVinci Resolve media pool without deleting source files from disk. Specify clip handles to remove.

Instructions

Delete clips from the media pool. This does not delete files from disk.

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": {
      "clip_handles": "<clip_handles>"
    },
    "name": "clip_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_handlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It states clips are removed from the media pool but not files from disk, which is a key behavioral trait. However, it omits details like reversibility, permission requirements, or effect on timeline references.

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 sentences, front-loaded with the purpose and an important caveat. Very concise, but could benefit from slightly more detail for completeness.

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

Completeness2/5

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

For a one-parameter tool with no output schema, the description is minimal. It lacks information about return values, error conditions, or effects on related resources, which is needed for confident use.

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 coverage is 0% and the description does not explain what 'clip_handles' are or their format. The description adds no semantic meaning beyond the schema for the only parameter.

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?

The description clearly states the tool deletes clips from the media pool and explicitly clarifies it does not delete files from disk. This distinguishes it from related sibling tools like clip_replace or clip_unlink.

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?

No guidance on when to use this tool vs. alternatives like clip_replace or clip_unlink. No prerequisites or exclusion criteria provided.

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