Skip to main content
Glama

markers

List, add, or delete timestamped timeline and clip notes by time, color, or custom data to organize edits and track feedback in DaVinci Resolve.

Instructions

Markers on the timeline, a timeline clip, or a media pool clip. target: 'timeline' | clip ref ('V1:0', id) | 'media:'. action: list | add | delete (at time, or all of color with time omitted; color 'All' = all) | delete_custom (by custom_data). For clips, time is seconds from the clip's start. duration in seconds.

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": "markers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
noteNo
timeNo
colorNoBlue
actionNolist
targetNotimeline
durationNo
custom_dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that omitting `time` deletes all markers of a given color and that color 'All' targets all markers, which is important destructive-scope information. It does not discuss permissions, irreversibility, or return behavior.

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?

The description is dense but front-loads the resource and then systematically explains targets, actions, and timing. It has little wasted wording, though the compressed syntax for clip/media references is somewhat cryptic.

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

Completeness3/5

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

For an 8-parameter, multi-action tool with no annotations and no output schema, the description covers the core invocation semantics reasonably well. It is still incomplete regarding return values, parameter `name`/`note`, and error or permission behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for most parameters: it defines target formats, action values, clip-relative `time`, color-all behavior, duration units, and custom_data usage. It omits explicit meaning for `name` and `note`, which keeps it from a 5.

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 names the resource (markers) and scopes it to timeline, timeline clips, or media pool clips. It also enumerates the supported actions (list, add, delete, delete_custom), so the tool's overall purpose is clear, though it does not explicitly distinguish itself from any sibling tool.

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?

The action and target values imply how to use the tool for listing, adding, or deleting markers, and the clip-relative time rule is stated. However, there is no explicit when-to-use guidance, no exclusions, and no comparison with alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.