Relocates a Premiere Pro project item or bin into a specified target bin path, organizing media by moving nodes between bins or to the project root.
Move a project item or bin into another bin
| Name | Required | Description | Default |
|---|---|---|---|
| nodeId | Yes | Project item nodeId (from get_project_items / find_project_items) | |
| targetBinPath | Yes | Bin path like 'Footage/Interviews' ('' = project 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 carries the full burden. It identifies this as a move mutation, but does not disclose side effects, whether existing target contents are overwritten, permission requirements, or reversibility.
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?
The description is a single, front-loaded sentence with no redundant or filler content.
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 mutation with complete schema descriptions, the description covers the core operation. However, with no annotations and no output schema, it should provide more behavioral context about what happens during the move.
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 adds a minor clarification that a bin itself can be moved, not just a project item, but otherwise defers to 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 uses a specific verb, 'Move', and names the resource precisely: a project item or bin into another bin. It implicitly distinguishes itself from timeline clip movement tools like move_clip, but does not explicitly name or contrast siblings.
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?
The description states what the tool does but gives no guidance on when to use it versus alternatives such as rename_project_item or create_bin. It also does not mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.