Skip to main content
Glama

delete_timelines

Destructive

Delete one or more timelines from a DaVinci Resolve project by passing their names or IDs.

Instructions

Delete timelines from the project.

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": {
      "timelines": "<timelines>"
    },
    "name": "delete_timelines"
  }
}

Input Schema

NameRequiredDescriptionDefault
timelinesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, and the description adds nothing beyond that: it does not say whether deletion is permanent, whether underlying media is removed, or whether confirmation is required. For a destructive mutation the description should carry more of the burden, even with annotations present.

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?

A single short, front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity reflects under-specification rather than tight writing of meaningful content.

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 destructive, single-parameter mutation with no output schema and no parameter documentation, the definition is too thin. It omits irreversibility, ID-vs-name semantics for the array items, and any error or partial-failure behavior.

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?

The single required parameter 'timelines' has 0% schema description coverage, and the description does not explain its shape at all. In particular the schema's anyOf[string, integer] (name or ID?) is left completely unexplained, so the description fails to compensate for the coverage gap.

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 concrete verb and resource: 'Delete timelines from the project.' An agent knows the operation and target scope without opening the schema. It does not differentiate itself from neighboring destructive tools (delete_bins, delete_clips, delete_project), so it falls short of a 5.

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 guidance on when to use this tool versus sibling deletion tools, no prerequisites, and no warning that this is a destructive, irreversible operation. The agent must infer the usage context entirely.

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