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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Install bridge panel into Premiere

premiere_install_bridge_panel

Installs the CEP bridge panel in Premiere Pro to enable unsigned extensions and place the panel in the Adobe CEP extensions folder. Restart Premiere and open Window > Extensions > Premiere MCP Bridge.

Instructions

Install the CEP bridge panel into Premiere for the current user (no admin): enables unsigned CEP extensions (PlayerDebugMode) and copies the bundled panel to the Adobe CEP extensions folder. After this, RESTART Premiere and open Window > Extensions > Premiere MCP Bridge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "premiere_install_bridge_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses key behavioral traits: 'no admin', enables unsigned CEP extensions, copies panel to Adobe CEP folder. With only openWorldHint annotation, the description carries the burden and provides specific, actionable details.

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 two sentences long, front-loaded with the action, and uses no unnecessary words. Every sentence adds value.

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?

Given no parameters or output schema, the description covers the purpose, the action taken, and a critical post-step. It does not explain the bridge panel's role, but the sibling tools provide context.

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?

No parameters in the schema, so the description does not need to add parameter info. Baseline for zero parameters is 4.

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 uses a specific verb ('Install') and resource ('CEP bridge panel into Premiere'), clearly distinguishing it from sibling tools that perform editing or other operations.

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

Usage Guidelines4/5

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

The description provides explicit post-install steps ('RESTART Premiere and open Window > Extensions > Premiere MCP Bridge'), giving context for use. However, it does not explicitly state when not to use or compare with alternatives like 'premiere_bridge_panel_status'.

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