Skip to main content
Glama

get_timeline

Read-only

Retrieve a DaVinci Resolve timeline's frame range, timecodes, playhead, tracks, markers and output blanking, with an option to include its settings.

Instructions

A timeline's frame range, timecodes, playhead, tracks (name, subtype, enabled, locked, item count), marks, markers, output blanking and optionally its settings.

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

Input Schema

NameRequiredDescriptionDefault
timelineNo
include_settingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes the return payload, which matters since there is no output schema, but it says nothing about scope resolution (does a null timeline mean the active timeline?) or what 'output blanking' and 'tracks' substructure look like in practice.

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?

A single dense sentence with no filler; every listed field is meaningful. It is slightly awkward as a sentence fragment that front-loads a possessive rather than a verb, but the information density is high and there is no redundancy.

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 zero schema coverage, the description does the minimum by enumerating return fields, which is genuinely useful. It falls short on the two things an agent still needs: what the timeline argument accepts and what the default behaviour is when it is omitted.

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 carry the parameter burden and largely does not. The 'optionally its settings' clause maps to include_settings, but the timeline parameter accepts string, integer or null and the definition never says whether that is a name, an index, an ID, or that null implies the current timeline.

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 definition reads as a noun-phrase inventory of what comes back from get_timeline: frame range, timecodes, playhead, tracks with name/subtype/enabled/locked/item count, marks, markers, output blanking. Combined with the tool name it is unambiguous that this retrieves a timeline's state, and the closing 'optionally its settings' distinguishes it from the get_timeline_settings sibling.

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 guidance and no mention of alternatives, despite siblings like get_timeline_settings, get_markers, playhead and get_current_frame_thumbnail existing. The definition also omits what happens when the timeline argument is omitted, which is the most likely decision point for an agent.

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