Skip to main content
Glama

project_export

Exports a DaVinci Resolve project to a .drp file or archives it as a .dra folder with source media when archive is enabled.

Instructions

Export a project to a .drp file, or archive it (.dra folder, with source media) when archive=true.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes
archiveNo
archive_mediaNo
with_stills_and_lutsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden: it usefully discloses the output artifact and that archiving bundles source media, which implies a potentially large, slow write. It does not mention overwrite behavior, permissions, or that this writes to disk at the given path.

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?

A single front-loaded sentence that names the default behavior first and the conditional mode second. Nothing is wasted and the key mode distinction is immediately visible.

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?

For a five-parameter, annotation-free mutation tool with no output schema, one sentence is thin. An agent still cannot tell what 'name' does or how 'archive_media' and 'with_stills_and_luts' alter the archive, so it may call the tool with defaults it did not intend.

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% across five parameters, and the description only explains one of them ('archive'). The meaning of 'name', 'archive_media' and 'with_stills_and_luts' — and how 'path' is interpreted for a folder vs a file — is left entirely undocumented.

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 and resource ('Export a project') and names the two concrete artifacts produced (.drp file vs .dra folder with source media). It is clear on its own, but it does not distinguish itself from sibling exporters such as quick_export, timeline_export or metadata_export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The only routing guidance is the inline condition 'when archive=true', which tells the agent when the archive branch applies. There is no statement of when to prefer this over sibling export tools, no prerequisites (e.g. project must be open), and no exclusions.

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