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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Run menu command (QE, experimental)

premiere_run_menu_command
Destructive

Execute any Premiere Pro menu command by its numeric ID. Use when no dedicated tool exists, but requires explicit confirmation.

Instructions

EXPERIMENTAL: execute a Premiere menu command by numeric ID via the unsupported QE DOM. Can be unstable/crash-prone -> requires confirm:true. Many actions have dedicated tools; prefer those.

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": {
      "menuId": "<menuId>"
    },
    "name": "premiere_run_menu_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
menuIdYesNumeric QE menu command ID.
confirmNoMust be true to proceed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Description explains experimental, unsupported nature and instability/crash risk, going beyond the destructiveHint annotation to inform agent behavior.

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?

Three short sentences, front-loaded with 'EXPERIMENTAL', each sentence adding essential info without waste.

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?

Covers purpose, risks, and usage guidance; lacks return value description but acceptable for experimental tool with no output schema.

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. Description restates 'requires confirm:true' but adds no new parameter meaning beyond schema descriptions.

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?

Description clearly states it executes a Premiere menu command by numeric ID via the QE DOM, distinguishing from sibling tools by noting dedicated tools exist for common actions.

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

Usage Guidelines5/5

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

Explicitly advises using dedicated tools when available, and requires confirm:true to proceed, providing clear when-to-use and when-not-to-use guidance.

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