DaVinci Resolve MCP Server

Overview Schema Source Related Servers Discussions Admin

set_project_setting

Set a specific DaVinci Resolve project setting by providing the setting key and its new value. Update project parameters programmatically for automated customization.

Instructions

Set a specific project setting.

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": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "set_project_setting"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full disclosure burden. It only states the action without mentioning overwrite behavior, prerequisites (e.g., an open project), return values, or error conditions, making behavior largely opaque.

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

Conciseness3/5

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

The description is a single concise sentence, but it omits critical details. While it is not verbose, it is under-specified rather than effectively concise, missing necessary information for correct use.

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 mutation tool with no annotations, no output schema, and zero parameter documentation, the description is inadequate. It doesn't address how keys/values are structured, any side effects, or usage constraints, leaving substantial gaps for an agent to operate correctly.

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?

The schema has 0% description coverage, and the description does not explain the 'key' or 'value' parameters, valid values, or expected formats. This fails to compensate for the schema gap.

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 identifies the tool as setting a project setting, using a verb+resource structure. However, it doesn't differentiate from other set_* siblings or explain what constitutes a project setting, so it's clear but not comprehensive.

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 usage context or alternatives are mentioned. The description gives no guidance on when to use this tool versus sibling tools like set_clip_property or set_track_name, leaving the agent uncertain about the appropriate context.

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