Skip to main content
Glama

import_bin

Import a .drb bin file into the current DaVinci Resolve bin and optionally relink its clips to a specified source path.

Instructions

Import a .drb bin file into the current bin (optionally relinking to source_clips_path).

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

Input Schema

NameRequiredDescriptionDefault
pathYes
source_clips_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is already conveyed. The description adds useful context beyond that: the operation targets the *current* bin (a state dependency) and can optionally relink to source clips. It does not disclose collision/overwrite behavior or permission requirements for a mutation tool.

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?

A single front-loaded sentence with the key object and destination stated first and the optional parameter noted parenthetically. No filler, though the parenthetical could be slightly clearer about what relinking does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers purpose, destination, and the optional relink behavior, which is nearly everything an agent needs. Edge cases such as existing-bin conflicts or missing current bin are the remaining gap.

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% for both parameters, so the description must carry the load. It usefully explains source_clips_path as relinking to source clips, which the bare title does not convey, but the required 'path' parameter's format and expectations remain undocumented beyond the implicit '.drb' file type.

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 ('Import') and resource ('.drb bin file') plus the destination ('into the current bin'), so an agent knows exactly what the tool does. It does not distinguish itself from siblings like import_project or import_media, so it stops short of a 5.

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 mention of 'current bin' implies a precondition (a bin must be selected), and 'optionally relinking to source_clips_path' hints at when that parameter applies. However, there is no explicit when-to-use versus import_media/import_project guidance and no statement of what happens if no current bin is set.

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