delete_bin
Delete a bin from the Premiere Pro project panel using its name or node ID.
Instructions
Delete a bin (folder) from the project panel
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bin_id | Yes | Name or node ID of the bin to delete |
Delete a bin from the Premiere Pro project panel using its name or node ID.
Delete a bin (folder) from the project panel
| Name | Required | Description | Default |
|---|---|---|---|
| bin_id | Yes | Name or node ID of the bin to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, so the tool's destructive nature is known. The description adds minimal extra context (location). Could expand on whether contents are also deleted.
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?
Single sentence, no fluff. Efficiently communicates the core action.
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?
Adequate for a simple destructive tool with one parameter and good annotations, but lacks detail on side effects (e.g., deletion of nested items) or return value. Still functional.
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?
Parameter bin_id is fully described in the schema (name or node ID). The description does not add new meaning beyond the schema, so baseline of 3 applies due to high schema coverage.
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 clearly states the action (delete), the resource (bin/folder), and the location (from the project panel). This distinguishes it from sibling tools like create_bin or rename_bin.
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?
No guidance on when to use this tool versus alternatives, such as move_item_to_bin or rename_bin. No prerequisites or conditions stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/leancoderkavy/premiere-pro-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server