DaVinci Resolve MCP Server

Overview Schema Source Related Servers Discussions Admin

append_to_timeline

Append named clips to the active DaVinci Resolve timeline. Provide clip names to add them to the end of your current sequence.

Instructions

Append clips to the current timeline by name.

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": {
      "clip_names": "<clip_names>"
    },
    "name": "append_to_timeline"
  }
}

Input Schema

Name	Required	Description	Default
`clip_names`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses that append targets the current timeline and uses names, but does not explain failure modes, whether clips are inserted at the playhead or end, or what happens if names don't match. This is thin for a 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.

Conciseness5/5

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

One sentence, no filler, directly states the operation and key qualifier. Perfectly concise and front-loaded.

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 1-param mutation tool with no annotations or output schema, the description is minimal. It omits prerequisites (current timeline existence), error handling, and behavior details like insertion position. This is insufficient for reliable invocation.

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?

The schema only defines clip_names as an array of strings with no description. The phrase 'by name' clarifies that the array elements are clip names used to identify clips, adding meaning beyond the schema. However, it doesn't specify the origin or validity requirements for these names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Append') plus resource ('clips') and target ('current timeline'), with method ('by name'). It clearly distinguishes from related tools such as create_timeline or set_current_timeline, which serve different purposes.

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?

The description implies usage: append to an existing current timeline, but does not explicitly state prerequisites such as having a current timeline set or alternatives like create_timeline_from_clips. There is no guidance on when not to use this tool, so the implied context is present but not elaborated.

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