DaVinci Resolve MCP Server

resolve_import_media

Import media files into the current DaVinci Resolve media pool bin using absolute file paths, returning names of successfully imported clips.

Instructions

Import media files into the current media pool bin.

Args: file_paths: List of absolute file paths to import (e.g., ["/Users/guy/video.mov"]).

Returns names of successfully imported clips.

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_paths": "<file_paths>"
    },
    "name": "resolve_import_media"
  }
}

Input Schema

Name	Required	Description	Default
`file_paths`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.0Sep 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden of explaining side effects alert, and it does state the core behavior: importing into the current bin and returning successful clip names. However, it does not disclose duplicate handling, unsupported file types, or failure behavior beyond returning names.

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 compact and organized with Args and Returns sections. Every sentence earns its place, and the key purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter import tool with an output schema, the description covers purpose, parameter semantics, and return behavior. It is complete enough for normal use, though edge-case behaviors and alternative tool selection are not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaning by specifying absolute file paths and providing an example. This compensates for the bare schema definition of 'file_paths' as an array of strings.

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 ('Import') and resource ('media files') and locates the action in the 'current media pool bin.' This clearly distinguishes the operation from siblings like resolve_list_media or resolve_find_media_clip.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it list exclusions or prerequisites. It only states the action and parameter, leaving usage decisions to inference.

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

Deploy Server