Skip to main content
Glama

delete_items

Destructive

Delete selected timeline items in DaVinci Resolve, with an optional ripple delete to close gaps left behind.

Instructions

Delete timeline items (optionally 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": {
      "items": "<items>"
    },
    "name": "delete_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
rippleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the core safety profile is covered. The description adds that ripple deletion is optional, which is useful behavioral context, but it does not explain what ripple actually does to neighboring items or whether deletion is reversible.

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?

The description is a single front-loaded sentence with no filler. Every word relates to the operation or its optional ripple behavior.

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?

This is a destructive operation with two parameters, zero schema description coverage, and no output schema. The one-sentence description is not complete enough: it leaves item identifier format, ripple consequences, and failure behavior unexplained for an agent invoking a destructive tool.

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%, so the description must compensate for undocumented parameters. It mentions items and ripple by name but does not explain what form the item identifiers take, whether items are clips/tracks/markers, or what ripple mode changes semantically.

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?

The description uses a clear verb and resource: deleting timeline items, with an optional ripple mode. However, 'items' is ambiguous against siblings such as delete_clips, delete_track, and delete_bins, and the description does not clarify the scope or relationship to those more specific deletion tools.

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?

It implies this is used for deleting timeline items but gives no guidance on when to choose it over delete_clips, delete_track, or other deletion siblings. There are no exclusions, prerequisites, or conditions beyond the optional ripple flag.

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