Skip to main content
Glama

create_bin

Create a bin (sub-folder) under a parent bin in DaVinci Resolve, defaulting to root. Use slash-separated names like "A/B/C" to build nested bins in one call.

Instructions

Create a bin (sub-folder) under parent (default: root). Use "A/B/C" in name to create nested bins.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
parentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It adds the root default for parent and the nested-path creation behavior, but says nothing about duplicate names, error cases, or whether intermediate bins are auto-created.

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?

Two short sentences, front-loaded with the action and with zero filler. The nesting syntax sentence earns its place, though the quoting of "A/B/C" is slightly awkward.

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 two-parameter creation tool with no output schema and clear annotations, the description covers the core semantics adequately. It is still thin on what is returned (bin identifier/path) and on collision or failure behavior when the path already exists.

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 coverage is 0%, so the description must carry parameter meaning; it does explain that parent defaults to root and that name accepts "A/B/C" path syntax, which is real value beyond the schema. However the type of parent (path string vs. identifier) and the return identity of the created bin remain unspecified.

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 ('Create a bin (sub-folder)') and clarifies the parent relationship, which distinguishes it from sibling delete_bins/export_bin. It doesn't explicitly name an alternative, but the resource and action are unambiguous.

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?

Usage is implied by the parent/default-root note and the nesting syntax, but there is no explicit when-to-use or when-not guidance relative to alternatives such as set_current_bin or create_project_folder.

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