premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Apply After Effects Render Handoff

apply_after_effects_render_handoff

Imports one previewed completed After Effects render into its approved Premiere bin after rechecking hosts and metadata, with confirmation and a preview token; returns the new projectItemId.

Instructions

Import exactly one previewed completed AE render into its approved Premiere bin after rechecking both hosts and file metadata. Requires confirmation and consumes the token before dispatch. Does not save, render, or change a timeline; the receipt returns the new projectItemId, and replace_clip swaps it in for an existing timeline clip at the same span.

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": {
      "preview_token": "<preview_token>",
      "confirm_import": "<confirm_import>"
    },
    "name": "apply_after_effects_render_handoff"
  }
}

Input Schema

Name	Required	Description
`preview_token`	Yes	One-time ten-minute token from preview_after_effects_render_handoff.
`confirm_import`	Yes	Must be true after reviewing the exact file and destination.
`idempotency_key`	No	Optional 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.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-idempotent; the description adds real behavior beyond that: a one-shot token is burned before dispatch (so a failure still spends it), hosts and file metadata are rechecked, and the timeline is left untouched. It also discloses that the receipt carries the new projectItemId. It stops short of describing failure/replay outcomes, which the idempotency_key schema field carries instead.

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 tight sentences, front-loaded with the action and destination, followed by prerequisites and then side effects/next step. Every clause carries information an agent needs before dispatch, with no restatement of the name or title.

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?

For a five-parameter mutation with nested CEP guards and an output schema, the description supplies the missing narrative: token lifecycle, host recheck semantics, absence of timeline mutation, and what the receipt yields. Remaining detail (parameter shapes, idempotency replay rules) is fully covered by the schema and 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 description coverage is 100%, so preview_token, confirm_import, idempotency_key, expected_cep_target and expected_project_path are already documented in detail. The description only echoes that confirmation is required and the token is consumed, adding little meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Import exactly one previewed completed AE render into its approved Premiere bin') and pairs it with a named sibling ('replace_clip swaps it in for an existing timeline clip'), so the agent can separate this apply step from the preview step and from timeline replacement without opening either schema.

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?

Gives when-to-use (only a previewed, completed render, after rechecking both hosts and file metadata), a hard prerequisite (requires confirmation and consumes the token before dispatch), and explicit when-not exclusions ('Does not save, render, or change a timeline'). It also routes the follow-up swap to replace_clip, covering all three guideline elements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server