Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by angelOnly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_timeline_marker

Add a marker to the current timeline at any frame in DaVinci Resolve, specifying name, note, and color to annotate edit points.

Instructions

Add a marker to the current timeline at a specific frame.

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": {
      "frame": "<frame>"
    },
    "name": "add_timeline_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
noteNo
colorNoBlue
frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden but only states the basic action. It fails to mention side effects, requirements, or how optional parameters behave, making behavior somewhat opaque.

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 redundancy. It conveys the core action efficiently.

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?

Given the lack of annotations and output schema, the description offers only minimal context. It does not mention the need for a current timeline, parameter details, or consequences, leaving the agent under-informed for reliable invocation.

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. It only hints at the 'frame' parameter via 'specific frame,' leaving name, note, and color entirely unexplained beyond their schema defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Add' and the resource 'marker to the current timeline' with a specific constraint 'at a specific frame.' This readily distinguishes it from sibling tools like add_track or add_color_node.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites such as needing an active timeline. The description is purely declarative.

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