Premiere Pro MCP Server

Preview Send Clip To After Effects

preview_send_clip_to_after_effects

Read-onlyIdempotent

Previews sending a timeline clip to After Effects like Replace with After Effects Composition, flagging unsupported clips and effects that would be lost, before applying the change.

Instructions

Preview sending one video timeline clip to After Effects, like Premiere's Replace with After Effects Composition. Reads the clip, its source media and the sequence, and the open saved AE project. Refuses speed-changed, reversed, offline or non-file clips. Lists effects and Motion/Opacity changes on the clip that the swap would not carry over. Changes nothing; returns a ten-minute token for apply_send_clip_to_after_effects.

Input Schema

Name	Required	Description
`node_id`	Yes	Node ID of the video clip on the active sequence.
`comp_name`	No	Optional composition name (default: '<clip name> Linked Comp'); a number is added if it is taken.
`target_bin_id`	No	Optional node ID of the Premiere bin for the linked comp (default: project root).
`ae_project_path`	Yes	The After Effects project open in AE, saved to disk. The comp is added to it and it is saved.
`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 one HTTP session) 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.
`approved_workspace_path`	Yes	Existing absolute folder that must contain ae_project_path.

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.

Addedv1.28.0Nov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by saying 'Changes nothing.' It adds meaningful behavioral context beyond annotations: which clips are refused (speed-changed, reversed, offline, non-file) and that effects plus Motion/Opacity changes would not carry over. It could mention token expiry/replay behavior more precisely, but the token lifetime is stated.

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?

The description is compact and front-loaded with the core preview action, then proceeds to refusals, what is not carried over, and the return token. Every sentence contributes actionable information with no 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 complex nested schema and the presence of an output schema, the description is complete enough: it explains the operation, the safety profile, refusal cases, loss reporting, and the handoff token. An agent has enough context to decide whether to call this preview and how it relates to the apply tool.

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 all eight parameters, including nested expected_cep_target fields, are already documented in the schema. The description references the clip, source, sequence, and AE project conceptually but adds no per-parameter guidance beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource ('Preview sending one video timeline clip to After Effects') and even maps it to Premiere's Replace with After Effects Composition concept. It clearly distinguishes itself from the sibling apply_send_clip_to_after_effects by emphasizing that it changes nothing and yields a token for that apply tool.

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?

It explicitly frames this as a preview step that changes nothing and returns a ten-minute token for apply_send_clip_to_after_effects, which tells the agent exactly when to use this versus the mutation sibling. The refusal conditions for unsupported clips add useful preconditions for deciding whether to attempt it.

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

Deploy Server