Skip to main content
Glama

render_timeline

Export the current DaVinci Resolve timeline in one call by queuing and rendering with presets, formats, codecs, resolution overrides, or a start/end range.

Instructions

One-shot export of the current timeline (queue + render + wait). E.g. preset 'YouTube - 1080p', or format='mp4', codec='H265'; width/height to override resolution; start/end for a range.

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

Input Schema

NameRequiredDescriptionDefault
endNo
nameNo
waitNo
codecNo
startNo
widthNo
formatNo
heightNo
presetNoH.264 Master
timeoutNo
settingsNo
target_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the call queues, renders and waits, which is the key behavioral trait. It omits what happens if wait is false (job handle returned?), where output lands (target_dir), and timeout behavior, so a mutation-class tool with real side effects remains only partly transparent.

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 dense sentences that front-load the core action, with concrete examples that earn their space. Slightly list-like, but there is no filler.

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?

For a 12-parameter export tool with no annotations and no output schema, the description should say what comes back and where the file goes. It covers the encoding options but not target_dir, wait/timeout semantics, or the return value, leaving an agent unable to predict the result of a call.

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% across 12 parameters, so the description must compensate, and it meaningfully explains preset (with an example value), format, codec, width/height and start/end. It leaves name, wait, timeout, settings and target_dir entirely unexplained, which is only half the surface area.

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 opens with a specific verb and resource, 'One-shot export of the current timeline', and the parenthetical '(queue + render + wait)' explains the composite action. It doesn't address the closely named sibling timeline_export, so an agent must infer the distinction, which keeps it from a 5.

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

Usage Guidelines3/5

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

'One-shot' signals this is the single-call, blocking path versus a staged queue-then-render workflow, which is useful implied guidance. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative, despite the many render_* siblings an agent could otherwise pick.

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