Skip to main content
Glama

export_bin

Exports a DaVinci Resolve bin to a .drb file for backup, transfer, or reuse.

Instructions

Export a bin to a .drb file.

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

Input Schema

NameRequiredDescriptionDefault
binYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is partly covered. However, the description adds nothing about what happens to an existing .drb at the target path (overwrite?), whether the bin must be open or current, or what is returned on success — all important for a file-writing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence has no wasted words and is front-loaded with the verb. However, its brevity is closer to under-specification than true conciseness, since key operational details are omitted entirely.

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 two-parameter file-writing tool with no output schema, the description should mention overwrite behavior, path expectations, and any post-export state. None of that is present, so an agent could invoke it correctly in shape but not confidently in semantics.

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 coverage is 0% for both parameters, so the description carries the full burden. It only hints that 'bin' identifies the source bin and 'path' is a destination .drb file; it does not clarify path format, whether it is a directory or full filename, or whether relative paths are allowed.

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 gives a specific verb ('Export') and resource ('a bin') plus the output artifact format ('.drb file'), so an agent knows exactly what the tool produces. It does not distinguish itself from siblings such as export_project or import_bin, leaving the agent to infer which export variant applies.

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 statement of when to use this tool versus export_project, quick_export, or import_bin, and no prerequisites or exclusions. The agent must infer the choice purely from the one-line purpose.

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