Skip to main content
Glama

export_timeline

Export a DaVinci Resolve timeline to AAF, EDL, FCP XML, FCPXML, DRT, OTIO, ALE, CSV, or HDR/Dolby Vision metadata by specifying the output path and format.

Instructions

Export a timeline: AAF (subtype aaf_new / aaf_existing), EDL (subtype none / cdl / sdl / missing_clips), FCP 7 XML, FCPXML 1.8-1.10, DRT, OTIO, ALE, CSV / tab text, HDR10 or Dolby Vision metadata.

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": {
      "path": "<path>",
      "format": "<format>"
    },
    "name": "export_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatYes
subtypeNonone
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The format list is capability disclosure, not behavioral disclosure. The description never says the tool writes a file to disk (implied only by the undocumented 'path' param and readOnlyHint=false), whether an existing file is overwritten, or what the response contains. With annotations giving only a bare safety profile and no explanation of why an export is not read-only, the burden falls on the description, and it does not meet it.

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 front-loaded sentence with a compact format/subtype list; no filler. The parenthetical subtype syntax is slightly dense but earns its place by mapping variants to formats.

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 4-parameter tool with a required path, a defaulted timeline, and no output schema or schema descriptions, the definition is missing critical invocation details: where the file is written, what 'timeline' accepts, and what is returned. It describes the menu of formats thoroughly but leaves the mechanics of calling it underspecified.

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 coverage is 0%, but the description partially compensates by coupling subtypes to formats (aaf_new/aaf_existing for AAF, none/cdl/sdl/missing_clips for EDL), which is real meaning beyond the enum. However, 'path' and 'timeline' — including the required path and the default-current-timeline behavior of 'timeline' — receive no explanation at all.

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?

States a specific verb ('Export') and resource ('a timeline') and enumerates the exact output formats, which lets an agent distinguish it from export_project, export_bin, or quick_export at a glance. It stops short of naming a sibling or scope boundary explicitly, so it is clear but not fully differentiated.

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 guidance and no mention of how this differs from the many sibling export_* tools. Prerequisites (must a timeline be current? does it export the current timeline by default?) are left entirely to inference from the schema defaults.

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