Skip to main content
Glama

move_items_to_bin

Move selected clips or assets into a specific bin in Adobe Premiere Pro to keep your project organized.

Instructions

Premiere Pro expanded operation: move items to bin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, and it discloses nothing beyond the action already implied by the name. It does not state whether items are moved from a current selection, whether the operation is destructive, what happens to the original location, or what 'expanded operation' means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified rather than appropriately concise. The phrase 'Premiere Pro expanded operation' adds no useful information, and the rest merely rewrites the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating Premiere Pro operation with no annotations, no output schema, and an empty input schema, this description is far from complete. An agent cannot determine what will be moved, how the destination bin is selected, what state must be prepared, or what success looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero declared parameters, so the empty schema leaves nothing for the description to document; the baseline for a no-parameter tool is 4. However, the schema's additionalProperties: true creates some ambiguity about whether arbitrary arguments are accepted, which the description does nothing to resolve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Premiere Pro expanded operation: move items to bin' is essentially a spaced-out restatement of the tool name plus a vague 'expanded operation' prefix. It names the action and object but never clarifies what counts as 'items', which bin is the target, or how this differs from the sibling move_item_to_bin.

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?

No usage guidance is provided. There is no indication of when to prefer this tool over the singular move_item_to_bin, whether it operates on selected items, or what prerequisites or context are required.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tro2789/scout-premiere-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server