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

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Preview After Effects Render Handoff

preview_after_effects_render_handoff
Read-onlyIdempotent

Preview importing a completed After Effects render into an existing Premiere bin, verifying file metadata and project/bin identity before handoff. Does not render, import, or edit timelines.

Instructions

Preview import of one completed After Effects single-file render into an existing Premiere bin. Reads both connected hosts and binds approval to file metadata and project/bin identity. Does not render, import, or edit a timeline.

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": {
      "approved_workspace_path": "<approved_workspace_path>",
      "output_path": "<output_path>",
      "ae_project_path": "<ae_project_path>",
      "premiere_project_path": "<premiere_project_path>",
      "queue_item_index": "<queue_item_index>",
      "target_bin_id": "<target_bin_id>"
    },
    "name": "preview_after_effects_render_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
output_pathYesExisting completed .mov, .mp4, .mxf, .avi or .wav render; image sequences are not supported.
target_bin_idYesExact node ID of an existing destination bin, never a name.
ae_project_pathYesExact open, saved After Effects project path.
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
queue_item_indexYesOne-based AE render queue item index, as returned by enqueue_after_effects_render.
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.
premiere_project_pathYesExact open, saved Premiere project path. It may be outside approved_workspace_path: it is only compared with the project Premiere has open.
approved_workspace_pathYesExisting absolute workspace containing both saved projects and the rendered media.

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: it reads both connected hosts (AE and Premiere) and binds approval to file metadata plus project/bin identity, which tells an agent this call is a cross-host verification rather than a pure file read. It stops short of describing what the approval artifact looks like, but an output schema exists to cover the response.

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: what it is, what it does under the hood, and what it explicitly does not do. The affirmative scope is front-loaded and every clause carries information an agent would otherwise have to guess.

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?

For a 9-parameter tool with nested objects, a full output schema and rich annotations, the description covers the essentials: preflight-only nature, dual-host read, identity-bound approval. The only soft spot is that it does not state the precondition that both AE and Premiere must be open and saved, though "Reads both connected hosts" and the schema's path descriptions gesture at it.

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 100%, including detailed per-parameter text for output_path, target_bin_id, queue_item_index, idempotency_key and the nested expected_cep_target. The description only echoes the concepts (single-file render, existing bin) that the schema already documents, adding no format, constraint or failure semantics of its own. Baseline 3 is warranted when the schema does all the parameter work.

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 names a specific verb and resource ("Preview import of one completed After Effects single-file render into an existing Premiere bin") and pins down scope: exactly one render, single-file only, an already-existing destination bin. The closing clause "Does not render, import, or edit a timeline" fences it off from the enqueue/render and apply-style siblings without needing to name them.

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 word "Preview" plus "binds approval" implies this is the dry-run step preceding an apply, but the description never states the condition that selects it over apply_after_effects_render_handoff or what to do with the approval afterward. Usage is inferable rather than prescribed.

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