Skip to main content
Glama

project_create

Create and open a new DaVinci Resolve project, optionally setting resolution, frame rate, and other project settings before timelines exist to avoid locked frame rate.

Instructions

Create and open a new project. Optionally set timeline resolution (width/height), frame rate (fps as string, e.g. '25', '29.97', '29.97 DF', '23.976'), and any other project settings. Set resolution/fps BEFORE creating timelines; Resolve locks fps once a timeline exists.

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

Input Schema

NameRequiredDescriptionDefault
fpsNo
nameYes
widthNo
folderNo
heightNo
settingsNo
media_locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose two real behavioral traits: the tool both creates and opens (changing active project state) and fps becomes immutable once timelines exist. It says nothing about what happens if a project of that name already exists, whether 'settings' overrides width/height/fps, or what the call returns.

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?

Front-loaded with the action, then a compact caveat sentence. Most wording earns its place, though 'and any other project settings' is loose filler that gestures at the undocumented settings object without adding information.

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?

For a nine-parameter-capable creation mutation with no annotations, no output schema, and zero schema descriptions, the definition covers the most failure-prone detail (fps format and lock timing) well. It remains incomplete on the opaque settings object, media_location, folder placement, and the result of the call, which an agent would need to invoke it confidently.

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

Parameters3/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 compensate. It does real work for fps, spelling out the accepted string forms including drop-frame and fractional rates like '29.97 DF' and '23.976', and clarifies that width/height mean timeline resolution. However, folder, settings (an opaque free-form object), and media_location are never mentioned, leaving three of seven parameters unexplained.

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 states a specific verb and resource ('Create and open a new project') and names the optional configuration surface (resolution, fps, other settings). It does not explicitly contrast with the sibling project_open, so the create-vs-open distinction must be inferred from the name alone.

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?

It gives a concrete ordering rule: 'Set resolution/fps BEFORE creating timelines; Resolve locks fps once a timeline exists.' That is genuine when-to-use sequencing guidance beyond the schema. It stops short of naming alternatives (project_open for existing projects) or stating preconditions such as required permissions or name collisions.

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