Skip to main content
Glama

move_bins

Moves one or more media pool bins into a target bin, helping reorganize DaVinci Resolve project media folders.

Instructions

Move bins into another bin.

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": {
      "bins": "<bins>",
      "target": "<target>"
    },
    "name": "move_bins"
  }
}

Input Schema

NameRequiredDescriptionDefault
binsYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/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 safety profile is partly covered. The description adds nothing about whether existing bins at the target are preserved, whether nesting depth is limited, or whether the operation is reversible — meaningful gaps for a mutation tool that nests one collection inside another.

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 short sentence with no filler and the object of the move stated up front. It is efficient, though the terseness is close to under-specification rather than disciplined brevity.

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?

With no output schema, zero schema description coverage, and a mutation annotation set that only rules out read-only and destructive behavior, the definition leaves the agent without enough information to call this reliably. Return shape, error conditions, and identifier conventions are all undocumented.

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%, so the description must carry parameter meaning and it largely fails: it does not say whether 'bins' holds IDs or names, whether the array may include the target itself, or how 'target' is identified. Only the loose bins-into-target relationship is implied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ('Move bins into another bin'), which is more than a tautology and implicitly distinguishes it from move_clips by naming bins. However, 'move' is ambiguous here: it could mean reparenting/nesting, reordering inside the target, or merging contents, and the sentence does not commit to one.

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 guidance on when to use this rather than move_clips or create_bin, no prerequisites (must the target bin already exist?), and no statement of what happens on failure. The agent must infer everything from the sibling names.

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