Skip to main content
Glama

set_timeline_start_timecode

Sets a timeline's start timecode from a supplied value so you can align edits, sync media, and match delivery specs in DaVinci Resolve.

Instructions

Set a timeline's start timecode, e.g. '01:00:00:00'.

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": {
      "timecode": "<timecode>"
    },
    "name": "set_timeline_start_timecode"
  }
}

Input Schema

NameRequiredDescriptionDefault
timecodeYes
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only but non-destructive, closed-world mutation, so the safety profile is covered. The description adds the concrete format '01:00:00:00' beyond the annotations, but it does not say whether existing clips, markers, or marks shift when the start timecode changes, nor whether the change is undoable.

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?

A single short sentence that front-loads the action and follows with a concrete example. No filler, no redundancy with the title or the schema.

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?

With no output schema and only two parameters, the definition is close to sufficient, and the format example covers the main ambiguity. It is still thin on the mutation's side effects — whether the timecode shift propagates to existing timeline items — which matters for an agent deciding whether to call it.

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?

Schema description coverage is 0%, so the description carries the burden; it partially discharges that by giving the required timecode's expected format. The optional 'timeline' parameter is left entirely unexplained — no hint whether it takes a name, an ID, or what null (the default) selects.

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 states a specific verb ("Set") and resource ("a timeline's start timecode"), so the effect is unambiguous. It does not distinguish itself from adjacent mutators such as set_timeline_settings, leaving the agent to infer which tool owns start-timecode changes.

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?

There is no when-to-use or when-not-to-use guidance, and no statement of prerequisites (e.g., that the timeline must exist or that null targets the current timeline). The only implied usage is "call this to change a start timecode," which the name already conveys.

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