premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Preview After Effects Render

preview_after_effects_render

Read-onlyIdempotent

Preview and validate a bounded After Effects render request for one named composition and existing workspace output directory; it does not contact Adobe, enqueue, or render.

Instructions

Preview a bounded queue-only After Effects render request for one named composition and existing workspace output directory. It does not contact Adobe, enqueue, or render.

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>",
      "composition_name": "<composition_name>",
      "output_path": "<output_path>",
      "render_settings_template": "<render_settings_template>",
      "output_module_template": "<output_module_template>"
    },
    "name": "preview_after_effects_render"
  }
}

Input Schema

Name	Required	Description
`output_path`	Yes	New workspace-contained output file path whose parent already exists.
`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.
`composition_name`	Yes	Exact existing After Effects composition name.
`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_module_template`	Yes	Exact After Effects output-module template name.
`approved_workspace_path`	Yes	Absolute operator-approved workspace root.
`render_settings_template`	Yes	Exact After Effects render-settings template name.

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavioral context by explicitly saying the tool does not contact Adobe, enqueue, or render, which is important for distinguishing a preview from an actual render operation.

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 two tightly written sentences with zero filler. The core action and scope are front-loaded, followed immediately by the critical non-actions.

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?

Given the output schema and rich input schema, the description does not need to explain return values or parameter details. It covers the essential operation and its non-actions, but for a complex tool with handoff and enqueue siblings, a brief note on when to choose this preview over those alternatives would improve completeness.

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 the detailed input schema already documents all eight parameters, including nested identity guards and idempotency behavior. The description only echoes the composition name and existing workspace output directory constraints without adding syntax or format detail beyond the schema.

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?

The description states a specific verb and resource ('Preview a ... After Effects render request') and scopes it to one composition and an existing workspace output directory. It also distinguishes itself behaviorally from enqueue/render tools by saying it does not contact Adobe, enqueue, or render, though it does not name the sibling alternatives.

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 description implies a dry-run/preview use case through 'It does not contact Adobe, enqueue, or render,' which helps an agent understand when it is appropriate. However, it gives no explicit when-to-use guidance and does not name alternatives such as enqueue_after_effects_render or the handoff preview/apply siblings.

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

Deploy Server