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

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Verify After Effects Connection

verify_after_effects_connection

Runs a read-only check that the After Effects CEP connector is active before commands, without reading project names, media, or paths.

Instructions

Read-only check that the dedicated After Effects CEP connector is running. It never reads project names, media, or paths.

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

Input Schema

NameRequiredDescriptionDefault
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

C2.8/5.0
Behavior1/5

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

The description asserts a 'Read-only check' while the annotations declare readOnlyHint=false, a direct conflict on the same attribute that could mislead an agent about the tool's side effects. The useful disclosure that it does not read project names, media, or paths is noted, but it cannot offset the explicit contradiction. Flagged as an annotation contradiction.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core behavior. The second sentence earns its place as a scope boundary, though a sentence on when to call it would have been more valuable than a second exclusion.

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

Completeness3/5

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

An output schema exists so return shape needn't be explained, but the description omits the two optional guard parameters and any notion of what a failed verification means for downstream AE commands. Adequate for a simple liveness check, incomplete for its role in the AE tool family.

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?

Both parameters (expected_cep_target, expected_project_path) are documented at 100% schema coverage with rich nested descriptions, so the schema carries the semantics. The description adds nothing about them — notably that they act as optional guards checked before AE commands — which leaves the schema to do all the work; baseline 3 applies.

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

Purpose4/5

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

Specific verb plus resource: a check that the After Effects CEP connector is running, with the 'After Effects' qualifier separating it from the Premiere-side verify_premiere_connection and the other AE tools (preview/enqueue_after_effects_render). It stops short of naming any sibling explicitly, so differentiation comes from the resource noun alone.

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?

States what the check is but never says when to call it — e.g., as a precondition before enqueue_after_effects_render or inspect_after_effects_render_templates — nor what to do when it fails. The only guidance is negative scope ('never reads project names, media, or paths'), which is a boundary rather than a usage rule.

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