Skip to main content
Glama

create_project

Create and open a new DaVinci Resolve project, optionally placing it inside a folder and setting a media location path for organized media management.

Instructions

Create and open a new project (optionally with a media location path, inside a folder).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
folderNo
media_locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-destructive, non-open-world write, so the safety profile is covered. The description adds real value by disclosing that the project is also opened (a state change beyond mere creation) and that media location and folder are optional. It does not say whether an existing project is closed, nor what is returned.

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?

One compact sentence with the core action front-loaded and options in a parenthetical. Slightly dense and parenthetical nesting costs a bit of readability, but there is no wasted wording.

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 three-parameter creation tool with no output schema, the definition omits what is returned (project identifier or object) and whether the new project becomes the active one immediately. Annotations cover the non-destructive write profile, so the remaining gaps are moderate rather than critical.

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 carries the burden, and it does name two of three parameters — a media location path and a parent folder. The required 'name' parameter is only implied by 'new project', and no format details (path style, folder identifier) are given.

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 plus resource ('Create ... a new project') and adds the side effect that the project is opened. This implicitly separates it from open_project and create_project_folder, though no sibling is named. An agent can tell the operation is a creation, not a settings change or open-only action.

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?

There is no explicit when-to-use guidance, no precondition (e.g. that a project must not already be open or that a folder must exist first), and no pointer to open_project for existing projects. Usage is only inferable from the verb 'Create'.

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