Skip to main content
Glama

delete_markers

Destructive

Deletes markers at a specified frame by color or custom data, with an All color option to remove every marker. Use it to clean up unwanted markers in DaVinci Resolve timelines.

Instructions

Delete markers at a frame, by color ('All' deletes every marker) or by custom data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
frameNo
targetNotimeline
custom_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 real value by warning that the 'All' color value wipes every marker, which amplifies the destructive scope beyond the annotation. It says nothing about reversibility, undo behavior, or what is returned, so it does not go much past the annotation floor.

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 sentence, front-loaded with the verb and resource, with the most dangerous mode called out parenthetically. Nothing is wasted, though the compressed 'or by custom data' phrasing makes the selector combination logic slightly ambiguous.

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, four-parameter mutation with zero schema documentation and no output schema, the description is too thin. An agent cannot tell what 'target' means, whether omitting frame deletes across the whole timeline, or whether the deletion is undoable.

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 carries the full burden and only partially meets it. It names color, frame, and custom_data and explains the special 'All' enum value, but never mentions the 'target' parameter (default 'timeline') and never clarifies what a null color or null frame does, which is the critical ambiguity given every parameter is optional.

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 pairs the verb 'Delete' with the resource 'markers' and enumerates the three selection axes (frame, color, custom data). The parenthetical that 'All' deletes every marker sharpens the scope. It does not name the read/add siblings, but the destructive verb alone separates it from add_markers and get_markers.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for removing markers rather than listing or adding them. There is no statement of preconditions, no guidance on when to prefer deleting by color versus by custom data, and no mention of when not to call it.

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