Skip to main content
Glama
Positronikal

DaVinci MCP Professional

by Positronikal

create_project

Start a new DaVinci Resolve project by providing a name. Initiates project creation to streamline video editing setup.

Instructions

Create a new project with the given name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name for the new project

Implementation Reference

  • The core handler that creates a project by calling the DaVinci Resolve API's CreateProject method. It checks if the project already exists, creates it, and sets it as the current project.
    def create_project(self, name: str) -> bool:
        """Create a new project."""
        self._ensure_connected()
    
        if not self._project_manager:
            return False
    
        # Check if project already exists
        projects = self.list_projects()
        if name in projects:
            raise ValueError(f"Project '{name}' already exists")
    
        result = self._project_manager.CreateProject(name)
        if result:
            self._current_project = self._project_manager.GetCurrentProject()
            logger.info(f"Created project: {name}")
    
        return bool(result)
  • Protocol type definition for the DaVinci Resolve ProjectManager.CreateProject method, showing the expected signature.
    def CreateProject(self, name: str) -> DaVinciProject | None:
        """Create a new project with the given name."""
        ...
    
    def LoadProject(self, name: str) -> DaVinciProject | None:
        """Load an existing project by name."""
        ...
  • Tool registration in the get_all_tools() function, defining the tool's name, description, and input schema (requires a 'name' string).
    types.Tool(
        name="create_project",
        description="Create a new project with the given name",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "The name for the new project",
                }
            },
            "required": ["name"],
        },
    ),
  • Server dispatch logic that routes the 'create_project' tool call from MCP to the DaVinciResolveClient.create_project method, extracting the 'name' argument and returning a formatted success/failure message.
    elif name == "create_project":
        name_arg = arguments.get("name", "")
        result = self.resolve_client.create_project(name_arg)
        return (
            f"Successfully created project '{name_arg}'"
            if result
            else f"Failed to create project '{name_arg}'"
        )
Behavior3/5

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

With no annotations, the description carries the full burden. It states that the tool creates a project, which implies mutation, but does not disclose any side effects, permissions, or error conditions. For a simple create operation, this is minimally adequate but not informative.

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, short sentence that conveys the essential action without redundancy. Every word earns its place.

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?

Given the simplicity of the tool (one parameter, no output schema, no annotations), the description is minimal but incomplete. It does not indicate the return value (e.g., project ID or object), which would help the agent understand the result of the creation.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it merely repeats 'with the given name'.

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 uses a specific verb 'Create' and resource 'project', clearly indicating the action. It distinguishes from siblings such as create_timeline (different resource) and list_projects (read operation).

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. For example, it does not mention that this tool is for creating a new project, while list_projects is for viewing existing projects, or open_project is for opening an existing one.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Positronikal/davinci-mcp-professional'

If you have feedback or need assistance with the MCP directory API, please join our Discord server