DaVinci Resolve MCP Server

by angelOnly

Overview Schema Source Related Servers Discussions Admin

Python

Local

start_project_render

Initiate rendering of the active DaVinci Resolve project, with optional preset selection and custom output path.

Instructions

Start rendering the current project with optional preset and path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_project_render"
  }
}

Input Schema

Name	Required	Description	Default
`preset_name`	No
`render_path`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says rendering 'starts' but does not indicate whether it is asynchronous or blocking, how long it might run, what happens to existing files, or what the result/return value looks like.

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 with no filler or repetition. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

Given the absence of annotations and output schema, this description is too sparse. It omits crucial context such as whether the operation is asynchronous, whether a project must already be open, what the preset_name and render_path parameters actually control, and what the tool returns or signals on completion.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate. 'Preset and path' merely echoes the schema's parameter titles ('Preset Name', 'Render Path'), and 'optional' is already implied by the default null values. No added meaning is provided regarding allowed values, formats, or semantics.

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 clearly states the specific action ('Start rendering') and the resource ('the current project'), and it mentions the optional preset and path. This distinguishes it from siblings like play_timeline or export_project, making the purpose unambiguous.

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 guidance on when to use this tool versus alternatives such as export_project or save_still. It also fails to mention prerequisites, such as needing a project to be loaded, or any exclusions.

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