DaVinci Director MCP

Overview Schema Source Related Servers Discussions Admin

davinci_create_vertical_project

Create a 9:16 vertical video project (1080x1920) at your specified frame rate, defaulting to 24fps, for social media editing.

Instructions

Creates or configures a 9:16 vertical project (1080x1920) at specified frame rate (default 24fps).

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": {
      "project_name": "<project_name>"
    },
    "name": "davinci_create_vertical_project"
  }
}

Input Schema

Name	Required	Description	Default
`fps`	No
`project_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

C2.7/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 burden of behavioral disclosure. It states 'creates or configures' but does not explain side effects, whether it overwrites existing projects, if any state is required, or what the response contains. For a mutation tool, this is insufficient.

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?

The description is a single, front-loaded sentence with no wasted words. It is appropriately concise, though the lack of detail reduces its effectiveness. Structure is fine but content could be richer.

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?

There is an output schema, which might cover return values, but the description does not reference it or explain what 'configure' entails. For a creation tool, it is missing crucial behavioral details like whether it creates a new project or modifies an existing one, and how the project is identified. The description is incomplete for safe usage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain parameters. It mentions frame rate and its default (24fps) but does not explain the 'project_name' parameter beyond its name. The description adds some meaning for fps but fails to clarify the required project_name, leaving it ambiguous.

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 states the tool creates/configures a 9:16 vertical project with specific resolution and frame rate. The verb 'creates or configures' is specific, though 'configures' is slightly vague. It distinguishes from siblings like create_vertical_timeline by focusing on project creation, but does not explicitly contrast 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 Guidelines2/5

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

No guidance on when to use this tool vs. alternatives such as davinci_create_vertical_timeline or davinci_set_vertical_resolution. There is no mention of prerequisites, when to choose this over others, or exclusions.

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