DaVinci Director MCP

Overview Schema Source Related Servers Discussions Admin

davinci_set_vertical_resolution

Set DaVinci Resolve project canvas to 1080x1920 vertical resolution, enforcing a 9:16 aspect ratio for vertical video editing.

Instructions

Enforces 1080x1920 (9:16 vertical) canvas resolution in DaVinci Resolve Project Settings.

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": "davinci_set_vertical_resolution"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Enforces' and 'Project Settings' but does not disclose side effects, prerequisites (e.g., an open project), failure modes, or whether the tool modifies existing settings versus creating new ones.

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, succinct sentence that delivers the essential information without any unnecessary detail or verbosity.

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

Completeness3/5

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

Given the simplicity of the action (setting a fixed resolution), the description is adequate but lacks surrounding context. It does not mention return values, effects on the current project state, or any required prior steps, which could be important for an agent to use the tool safely.

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?

The tool has zero parameters, so the description does not need to explain any. The fixed resolution is clearly stated in the description, providing sufficient meaning for a parameterless operation.

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 tool's function: enforcing a specific canvas resolution (1080x1920, 9:16 vertical) in DaVinci Resolve Project Settings. It distinguishes itself from sibling tools by focusing on the resolution setting, not project creation or timeline setup.

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 does not provide any guidance on when to use this tool versus alternatives like davinci_create_vertical_project or davinci_create_vertical_timeline. It only states what it does, leaving the agent to infer the appropriate context.

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