Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create bin

premiere_create_bin

Creates a new bin in the project to organize media. Optionally place the bin inside an existing parent bin for structured organization.

Instructions

Create a new bin (folder) in the project, optionally inside an existing parent bin.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new bin.
parentBinNameNoExisting parent bin (defaults to root).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the creation action and optional nesting, which is sufficient. However, it does not mention side effects like project modification or permission needs.

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

Conciseness5/5

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

The description is one sentence, front-loaded with the verb and resource, and contains no unnecessary words.

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

Completeness4/5

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

The description is complete enough for a simple creation tool with no output schema. It covers the essential behavior, though it could mention that the bin is added to the current project.

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 coverage is 100%, so baseline 3. The description adds 'optionally inside an existing parent bin' which is already implied by the schema description for parentBinName. Minimal added value.

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

Purpose5/5

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

The description clearly states the tool creates a bin (folder) in the project, with an optional parent bin. This is a specific verb-resource pairing and distinguishes it from sibling tools like create_sequence or import_files.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (to organize project items) but provides no explicit when-not or alternatives. It is adequate for a straightforward creation tool.

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

Deploy Server

Other Tools