Skip to main content
Glama

import_timeline

Imports timelines from AAF, EDL, XML, FCPXML, DRT, ADL, or OTIO into the current DaVinci Resolve project, with optional source clip import and naming.

Instructions

Import a timeline from AAF / EDL / XML / FCPXML / DRT / ADL / OTIO into the current project.

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>"
    },
    "name": "import_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
timeline_nameNo
source_clips_binsNo
source_clips_pathNo
import_source_clipsNo
interlace_processingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false, and destructiveHint=false, so the description must carry the rest. It never says whether a new timeline is created, whether an existing one is replaced or renamed, what happens to the current project state, or how source-clip import interacts with the timeline. For a mutation tool with six parameters, that is a substantial gap.

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 front-loaded sentence with no filler; the format list earns its place by conveying capability up front. It is tight, though its brevity comes at the cost of the parameter and behavior detail the tool needs.

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 exists and six parameters are undocumented, including a source-clip import flag defaulting to true that could materially change results. For a mutation tool in a crowded import family, the description is too thin to call correctly without opening the schema and guessing.

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 compensate for six parameters and explains none of them. Only 'path' is loosely implied by the format list; timeline_name, source_clips_bins, source_clips_path, import_source_clips (default true), and interlace_processing are never mentioned or clarified.

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 states a specific verb (import) and resource (timeline) and enumerates the supported formats (AAF/EDL/XML/FCPXML/DRT/ADL/OTIO), which is genuinely informative. It does not differentiate from siblings like import_into_timeline or import_media, leaving the agent to infer the distinction.

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 guidance on when to use this versus import_into_timeline, import_media, or import_project, and no prerequisites or caveats. The agent is told what the tool does but not when it is the right choice.

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