Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by angelOnly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

import_timeline_from_file

Import a timeline from an XML or EDL file into DaVinci Resolve, preserving edit decisions for further editing.

Instructions

Import a timeline from a file (e.g., XML, EDL).

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": {
      "file_path": "<file_path>"
    },
    "name": "import_timeline_from_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects but only states 'Import' without explaining whether it overwrites the current timeline, requires an open project, or returns status information. This is a notable gap for a potentially mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the verb and object, with no filler or redundant content. It is appropriately sized for a simple tool.

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?

The tool has a simple schema and no output schema, but the description still lacks critical context such as side effects, supported file formats in detail, and whether the operation appends or replaces. This makes it only partially complete for an agent to use confidently.

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?

The single parameter file_path is self-explanatory, but the description only gives examples (XML, EDL) and does not clarify path format, supported extensions beyond examples, or any constraints. With 0% schema coverage, the description partially compensates but remains insufficient.

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 clearly states the action (import) and the resource (timeline from a file), making its purpose unambiguous. It is distinct from sibling tools like import_project or import_media by focusing on timeline data, though it does not explicitly contrast with them.

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 is provided on when to use this tool versus alternatives such as import_project, create_timeline, or append_to_timeline. The description lacks context on prerequisites, use cases, or when not to use it.

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