Skip to main content
Glama

playhead

Read the current timeline position or move it to a specified time in seconds, frames, or timecode within DaVinci Resolve.

Instructions

Get the playhead, or move it to time (seconds from timeline start, '120f' or timecode).

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

Input Schema

NameRequiredDescriptionDefault
timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the get/set duality but does not say what a get returns, whether moving the playhead is undoable or affects selection, or how invalid time formats are handled.

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?

One sentence, front-loaded with the core behavior and the sole parameter's formats in a compact parenthetical. There is no unnecessary wording.

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 a one-parameter utility, it covers the essential get/set behavior and input format. Without an output schema, however, it should say what a get returns and confirm the playhead's scope, leaving some behavioral gaps.

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 parenthetical is critical: it defines the time unit as seconds from timeline start and accepts '120f' or timecode. It leaves the exact timecode syntax and the null/default behavior only implied.

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 resource, 'playhead', with two clear verbs: get and move. It also explains the condition for moving, though it does not explicitly differentiate from siblings; none of the listed siblings appear to be a playhead alternative.

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

Usage Guidelines4/5

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

The sentence makes the conditional explicit: omit time to read the playhead, provide time to move it. No exclusions or named alternatives are given, but the core when-to-use distinction is clear.

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