Skip to main content
Glama

delete_track

Destructive

Removes a video, audio, or subtitle track and all content on it from a DaVinci Resolve timeline by track type and index, optionally targeting a specific timeline.

Instructions

Delete a track and everything on it.

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": {
      "track_type": "<track_type>",
      "index": "<index>"
    },
    "name": "delete_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
timelineNo
track_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety class is known. The description adds real value with "and everything on it," clarifying that child items are destroyed too, but it omits irreversibility/undo availability and any permission or confirmation requirements.

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 front-loaded sentence with no filler or redundancy. It is efficient, but the terseness borders on under-specification rather than tightness.

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, three-parameter tool with no output schema and no parameter documentation, the description should explain the index/timeline interplay and what is returned or lost. It covers only the highest-level fact, leaving the agent without enough to call it correctly.

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% across three parameters, so the description carries the full burden and fails to explain them. It never clarifies what index refers to (positional order that shifts after deletion), what timeline does when null (defaults to the active timeline?), or that track_type selects the track namespace.

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 a track") and adds scope with "and everything on it," which tells the agent the blast radius. It does not distinguish itself from siblings like update_track or delete_timelines, so the agent must infer the boundary.

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 mention of alternatives for removing only some content (e.g., delete_clips / delete_items), and no precondition such as requiring an open project or the track being empty. The agent gets no routing signal beyond the name.

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