Skip to main content
Glama

filmcraft_create_bin

Creates a new organizational bin or folder in the FilmCraft project panel, with optional parent-bin nesting, so you can group project assets.

Instructions

Creates a new organizational bin/folder in the FilmCraft project panel.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the bin (e.g., 'Selects', 'SoundFX', 'Graphics')
parentBinIdNoOptional parent bin ID for nested structure

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/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 doesn't say whether a project must be open, what happens on duplicate names, whether the created bin becomes selected, or whether a bin ID is returned for chaining into parentBinId.

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 no filler; the verb and resource lead. It is efficient, though its brevity contributes to the gaps elsewhere rather than being a flaw in structure itself.

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 a fully documented schema and no output schema, the description is minimally sufficient to call the tool. Missing are the operational preconditions and the notion that the created bin's identifier matters for follow-up calls, which an agent would need.

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 100% — both 'name' and 'parentBinId' have examples and meaning in the schema. The description adds nothing about nesting or naming constraints beyond that, so the baseline 3 applies.

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 (creates) and resource (organizational bin/folder) plus where it lands (FilmCraft project panel), which is more than a restatement of the name. No sibling tool in the list creates bins, so differentiation is implicitly handled, though not called out.

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?

The description gives no when-to-use guidance, no prerequisites (an open project is presumably required), and no contrast with siblings like filmcraft_import_media or filmcraft_new_project. The agent must infer usage entirely.

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