Premiere Pro MCP Server

Preview Mogrt Recipe

preview_mogrt_recipe

Read-onlyIdempotent

Preview an After Effects MOGRT recipe to validate your workspace output directory and template parameters without writing files or contacting Adobe.

Instructions

Preview a bounded After Effects MOGRT recipe from the supported title, callout, quote, social, and media-placeholder template library. It validates one existing workspace output directory but does not contact Adobe or write any files.

Input Schema

TableJSON Schema

Name	Required	Description
`width`	No	Composition width from 320 to 7680 pixels; defaults to 1920.
`height`	No	Composition height from 240 to 4320 pixels; defaults to 1080.
`recipe`	No	Supported authored template recipe; defaults to lower_third.
`headline`	Yes	Primary headline text, at most 160 characters. Required for text recipes; optional caption for media_placeholder.
`subtitle`	No	Optional secondary lower-third text, at most 160 characters.
`brand_kit`	No	Optional approved local brand kit. It can constrain naming, request an installed font, place a workspace-contained PNG/JPEG logo, and enforce a safe margin.
`frame_rate`	No	Composition frame rate; defaults to 30.
`text_color`	No	Optional text color as #RRGGBB; defaults to #FFFFFF.
`accent_color`	No	Optional accent fill color as #RRGGBB; defaults to #2563EB.
`template_name`	Yes	Safe template file stem; the generated artifact is template_name.mogrt.
`text_controls`	No	full (default) also exposes per-text-layer Font Size, Fill Color, Stroke Color, Stroke Width, Position, Scale, Rotation, Anchor Point, and Opacity controls; text_only exposes only the text strings.
`duration_seconds`	No	Composition duration between 2 and 30 seconds; defaults to 5.
`output_directory`	Yes	Existing absolute output directory inside approved_workspace_path; this workflow never creates directories.
`placeholder_media_path`	No	Required for media_placeholder: absolute workspace-contained PNG, JPEG, MOV, or MP4 placed as the swappable Essential Graphics media slot.
`approved_workspace_path`	Yes	Absolute operator-approved workspace root containing the saved AE project and output directory.

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / properties / brand_kit / properties / font_family / description

Added value: +"PostScript font name for the template text (for example Halogen-Bold). Use a font from Adobe Fonts: After Effects will not export a template with other fonts unattended."

addedInput schema / properties / brand_kit / properties / safe_margin_percent / description

Added value: +"Title-safe margin: 2-25 (percent) or 0.02-0.25 (fraction of the frame); default 10%."

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed4 schema fields changedv1.18.0Sep 23, 2026

changedInput schema / properties / headline / description

Previous value: -"Primary lower-third text, at most 160 characters."New value: +"Primary headline text, at most 160 characters. Required for text recipes; optional caption for media_placeholder."

addedInput schema / properties / placeholder_media_path

Added value: +{
+  "description": "Required for media_placeholder: absolute workspace-contained PNG, JPEG, MOV, or MP4 placed as the swappable Essential Graphics media slot.",
+  "type": "string"
+}

changedInput schema / properties / recipe / enum

Previous value: -[
-  "lower_third",
-  "title_card",
-  "callout",
-  "quote_card",
-  "social_end_card"
-]New value: +[
+  "lower_third",
+  "title_card",
+  "callout",
+  "quote_card",
+  "social_end_card",
+  "media_placeholder"
+]

addedInput schema / properties / text_controls

Added value: +{
+  "description": "full (default) also exposes per-text-layer Font Size, Fill Color, Stroke Color, Stroke Width, Position, Scale, Rotation, Anchor Point, and Opacity controls; text_only exposes only the text strings.",
+  "enum": [
+    "full",
+    "text_only"
+  ],
+  "type": "string"
+}

Addedv1.14.9Sep 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is low; the description still adds real value by stating it does not contact Adobe and does not write files, and that it validates exactly one existing workspace output directory.

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?

Two tight sentences, front-loaded with what is previewed and immediately followed by the key constraint (no Adobe contact, no writes). No padding or repetition of structured fields.

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 15-parameter, nested, enum-heavy tool with an output schema, the description covers the core intent and the safety-relevant behavior. It stops short of clarifying the preview-versus-commit boundary relative to create_mogrt_recipe, but the return format is handled by the 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% across 15 parameters with enums and a nested brand_kit object, so the schema already carries the semantic load. The description only adds the general template-library framing and no per-parameter detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb (Preview), resource (After Effects MOGRT recipe), and scope (bounded, drawn from the supported template library), which distinguishes it from create_mogrt_recipe and verify_mogrt_artifact. It does not name those siblings directly, so the differentiation is inferential rather than explicit.

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 establishes the preview context and notes it validates one existing output directory rather than writing files, implying a dry-run check. However it never states when to choose this over sibling preview/create/verify MOGRT tools, leaving usage to inference.

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

Deploy Server