Skip to main content
Glama

set_timeline_settings

Configure DaVinci Resolve timeline parameters such as custom settings, resolution width, and frame rate, with failing keys retried individually and reported.

Instructions

Set timeline settings (e.g. useCustomSettings, timelineResolutionWidth, timelineFrameRate...). Keys failing as a group are retried one by one and reported.

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": {
      "settings": "<settings>"
    },
    "name": "set_timeline_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYes
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuinely useful behavior beyond that: failures are retried per-key rather than aborting the whole call, and results are reported back. It still leaves open what a partial failure returns and whether existing unlisted settings are preserved, which matters for a settings-mutation 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?

Two short sentences, front-loaded with the operation and followed by the noteworthy failure-handling behavior. The trailing ellipsis in the key list is slightly sloppy but does not obscure meaning or waste space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with a nested free-form object and no output schema, the definition covers the essentials: what it sets, example keys, and the non-obvious per-key retry semantics. The only real gap is the meaning of the optional 'timeline' parameter, which is minor against an otherwise complete picture.

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% and the 'settings' object is free-form with additionalProperties, so the example key names are real added value that the schema cannot supply. However, the second parameter 'timeline' is never explained — its default of null and whether null means 'current timeline' is left unstated, so the description only half compensates for the coverage gap.

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 gives a specific verb and resource ('Set timeline settings') and names concrete setting keys (useCustomSettings, timelineResolutionWidth, timelineFrameRate), which makes the target of the operation unambiguous. It does not differentiate itself from siblings like set_project_settings or set_render_settings, but the resource noun carries that distinction reasonably well.

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 guidance on when to use this tool versus get_timeline_settings, set_project_settings, or set_render_settings, and no mention of prerequisites or which timeline is affected when the 'timeline' parameter is omitted. The agent must infer usage entirely from the name and the read/write sibling pairing.

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