Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by angelOnly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_playhead_position

Pinpoint any frame in the current timeline by moving the playhead to that location, enabling quick navigation and review.

Instructions

Set the playhead position to a specific frame in the current timeline.

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

Input Schema

NameRequiredDescriptionDefault
frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 of behavioral disclosure. It only states the immediate action and omits side effects (e.g., impact on playback), frame validity constraints, and error handling. For a mutating operation, this is a significant gap.

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, direct sentence with no redundancy. It gets straight to the point and is easy to scan.

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 simple tool, the description still lacks essential operational details: what happens if the frame is out of range, whether playback is stopped, and whether a current timeline must already be set. With no output schema and no annotations, these gaps make the description incomplete.

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

Parameters3/5

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

The schema only defines 'frame' as an integer, and the description repeats the concept of a 'specific frame' without adding units, indexing (0- or 1-based), or range bounds. It provides some context but does not fully compensate for the 0% schema description coverage.

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 a specific action ('set the playhead position') with a target ('to a specific frame') and context ('in the current timeline'). This distinguishes it from siblings like set_current_timeline or play_timeline.

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 description implies the tool is used to move the playhead to a precise frame, but it does not explicitly provide guidance on when to use it versus alternatives, nor does it mention prerequisites (e.g., having a current timeline). No exclusions or preferred scenarios are mentioned.

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