Skip to main content
Glama

get_timeline_settings

Read-only

Retrieves timeline settings from DaVinci Resolve, optionally filtered by specific keys, so agents can inspect configuration before making timeline changes.

Instructions

Timeline settings (all or keys); see get_api_type('TimelineSettings').

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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/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 and there is no contradiction. Beyond that the description adds nothing: no hint about defaults returned, cost of fetching all settings, whether the timeline parameter falls back to the current timeline, or the shape of the response, which is instead delegated to another tool.

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?

One short clause plus a cross-reference, front-loaded with the resource and scope, with no filler. It is efficient, though the cross-reference does shift real explanatory work onto another tool call.

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?

No output schema and zero schema coverage, so the definition should describe what the settings object contains and how `timeline` resolves. Instead it defers the payload contract to get_api_type('TimelineSettings'), leaving an agent unable to call it correctly without a second tool call.

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 parameter meaning. It explains only that omitting `keys` yields all settings; the format of key strings and the entire `timeline` parameter (string or integer, defaulting to null) are left unexplained.

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

Purpose3/5

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

The text names the resource ('Timeline settings') and hints at scope ('all or `keys`'), and the get_ prefix plus the sibling set_timeline_settings imply the read/write split. But there is no verb in the description itself and 'Timeline settings' largely restates the tool name, so differentiation rests on naming conventions rather than stated evidence.

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 statement of when to call this versus set_timeline_settings, get_timeline, or get_project_settings; the only pointer is a follow-up reference to get_api_type for the settings shape. The 'all or `keys`' fragment implies a narrowing mode but never says when to use which.

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