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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Restart Premiere

premiere_restart
Destructive

Restarts Adobe Premiere Pro by gracefully closing it, waiting, and then launching it again, with the option to reopen a specific project.

Instructions

Gracefully close Premiere, wait, then start it again (optionally reopening a project). Requires confirm:true. Premiere may show a save prompt during close.

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_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
projectPathNoProject to reopen after restart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description reveals graceful closing, a wait period, and the possibility of a save prompt during close. This additional behavioral context helps the agent anticipate user interaction.

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?

Two short sentences that immediately convey the action and key requirements. No unnecessary words or repetition.

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

Completeness5/5

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

Given the tool's simplicity (no output schema, few parameters), the description covers the restart process, required confirm flag, optional project reopening, and potential save prompt. It is sufficient for an agent to understand and use the tool correctly.

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 description coverage is 50% (only projectPath described). The description adds that confirm must be true, partially compensating for the undocumented confirm parameter, but doesn't elaborate further on parameter values or constraints.

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 restarts Premiere, specifying the sequence (close, wait, start again) and the optional project reopening. This is distinct from sibling tools like premiere_launch, premiere_quit, and premiere_open_project.

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 explicitly requires confirm:true, and notes the optional projectPath parameter. While it doesn't contrast with alternatives, the tool's specific restart function and the stated requirement provide clear guidance for correct invocation.

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