Creates a new bin (folder) in the Premiere Pro project panel to organize clips and assets. Specify a name and optional parent path for nested structure.
Create a new bin (folder) in the project panel
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name for the new bin | |
| parentBinPath | No | Parent bin path (empty for root) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral burden. It does not disclose what happens on duplicate names, whether the bin is created selected/visible, error conditions, permissions, or what the tool returns after creation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with the verb and resource front-loaded. It is appropriately sized, though it could have used the space to add usage or behavioral context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter creation tool with full schema coverage and no output schema, the description is minimally sufficient. However, with no annotations it leaves mutation behavior and failure modes entirely unexplained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters are already documented in the input schema. The description's parenthetical '(folder)' adds a small clarifying synonym for 'bin' but no additional parameter semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Create') and resource ('a new bin (folder)') and locates it ('in the project panel'). It is clear enough to distinguish from sibling tools like create_sequence or create_sub_clip, though it does not explicitly contrast with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 tool versus alternatives such as import_media or create_sub_clip, nor any prerequisites. Usage is only implied by the verb 'Create'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.