Skip to main content
Glama

bin_manage

Manages bins and clips in DaVinci Resolve: create, select, move, export, import, or refresh bins, and delete clips or bins when needed.

Instructions

Bins/clips housekeeping. action: 'create' (path, nested ok) | 'select' (make path the current bin) | 'move' (items → target bin; items may be clip refs or bin paths) | 'delete' (items = clips/timeline clips, or bin paths prefixed 'bin:') — irreversible | 'export' (bin path → .drb file) | 'import' (.drb file into current bin) | 'refresh'.

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": {
      "action": "<action>"
    },
    "name": "bin_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
pathNo
itemsNo
actionYes
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does flag that 'delete' is irreversible and that items may be clip refs, timeline clips, or 'bin:'-prefixed paths, which is genuinely useful. However, it says nothing about permissions, confirmation requirements, what happens to contained clips when a bin is deleted, what 'refresh' actually does, or what any action returns, leaving major behavioral gaps for a mutation-capable 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?

One dense, front-loaded block using pipe-delimited action clauses; nearly every phrase carries information about an operation or its operands. The trailing '| refresh.' is an unearned stub that adds a value name without meaning.

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 seven-action dispatcher with five parameters at 0% schema coverage and no output schema, the description covers action values and operand roles adequately but leaves 'refresh' undefined, does not state that action is required, and never explains return behavior such as whether create/select return the resulting path. Minimum viable for its complexity, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does: it supplies the action value set (absent from the schema, which has no enum), explains path as a bin path made current or exported, explains items as clip refs or bin paths, and implies target as the destination bin, plus file as the .drb artifact. Gaps remain — 'target' is never named explicitly and 'refresh' takes no operand guidance — but the coverage is well above what the schema alone provides.

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 resource (bins/clips) plus 'housekeeping' and enumerates the exact operations available via the action parameter ('create', 'select', 'move', 'delete', 'export', 'import', 'refresh'), so an agent knows precisely what the tool covers. It does not differentiate from plausible siblings such as project_manage or timeline_manage, which keeps it below 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?

Each action is annotated with its operand shape (create takes path, select makes path current, move sends items to a target bin, export writes to a .drb file), which implicitly routes the agent to the right action. There is no explicit when-to-use/when-not or comparison against alternative tools, so guidance is implied rather than stated.

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