Skip to main content
Glama

set_project_settings

Configure DaVinci Resolve project settings from key-value pairs, with automatic per-key retries and failure reporting when Resolve rejects the full dictionary.

Instructions

Set project settings from a {key: value} dict (see get_api_type('ProjectSettings')). If Resolve rejects the whole dict, keys are retried one by one and the failing ones reported. The 'superScale' 2x Enhanced mode needs execute_python: project.SetSetting('superScale', 2, sharpness, nr).

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": {
      "settings": "<settings>"
    },
    "name": "set_project_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, and the description adds genuinely new behavior: the dict is applied per-key with retry on whole-dict rejection, and failing keys are reported. That non-atomic partial-application semantics is exactly the kind of thing annotations cannot convey. It does not say what the failure report looks like or whether successful keys persist after a partial failure.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, then the failure semantics, then the edge case. The final snippet ('sharpness, nr') uses unexplained placeholder names, but the overall density is high with little waste.

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 generic-dict mutation tool with no output schema, it covers key discovery, partial-failure behavior, and the one known exception requiring another tool. The main remaining gap is the return value and whether a partially applied update is rolled back.

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 coverage is 0% and the single parameter is an unconstrained object with additionalProperties, so the description carries the burden — and it does, explaining that keys are ProjectSettings keys discoverable via get_api_type and giving a concrete superScale example. It still leaves the value types and any key-specific constraints undocumented.

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?

States a specific verb and resource ('Set project settings') and names the shape of the input ('a {key: value} dict'). It is clearly distinguishable from get_project_settings and from the render/timeline settings siblings by the 'project' scope, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete discovery path for the caller ('see get_api_type(\'ProjectSettings\')') and an explicit when-not case: the 'superScale' 2x Enhanced mode must go through execute_python instead. It stops short of stating prerequisites or when to prefer get_project_settings first, but the routing guidance is real.

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

Deploy Server

Other Tools