DaVinci Resolve MCP Server

resolve_export_lut

Export the current clip's color grade as a .cube LUT file at a specified output path, with selectable cube sizes (17pt, 33pt, or 65pt) for use in other grading software.

Instructions

Export a LUT from the current clip's grade.

Args: output_path: Absolute path for the output .cube file. export_type: "17pt", "33pt" (default), or "65pt".

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": {
      "output_path": "<output_path>"
    },
    "name": "resolve_export_lut"
  }
}

Input Schema

Name	Required	Description	Default
`export_type`	No		33pt
`output_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.0Sep 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden; it does disclose the core side effect by specifying an output .cube file at an absolute path. It does not discuss overwrite behavior, prerequisites for the current clip, or failure modes, but the main write action is clear enough for a straightforward export 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 two compact parts: a front-loaded purpose sentence and a terse args list. There is no filler or repetition beyond what is needed to document the parameters.

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 simple two-parameter tool with an output schema and full parameter descriptions, the description is nearly complete. The main residual gap is that 'current clip' is not defined and no usage alternative is given, but the operation and its inputs are sufficiently clear.

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

Parameters5/5

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

Since schema description coverage is 0%, the description fully compensates by defining output_path as an absolute .cube path and enumerating the allowed export_type values (17pt, 33pt default, 65pt). This adds real meaning beyond the bare schema types and default.

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 opening sentence names a specific verb (export), a specific resource (LUT), and a source scope (current clip's grade). This cleanly separates it from sibling tools like resolve_apply_lut and resolve_get_lut, which involve applying or retrieving rather than creating a .cube file.

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 conveys when the operation is relevant (exporting a LUT from the current grade), but it gives no explicit guidance on alternatives or exclusion conditions. It does not mention that resolve_apply_lut and resolve_get_lut are for other LUT operations, so usage is only implied by the purpose statement.

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

Deploy Server