Premiere Pro MCP Server

Preview Mogrt Batch

preview_mogrt_batch

Read-onlyIdempotent

Preview up to 20 bounded MOGRT recipe exports from a workspace-contained JSON or CSV file to validate batch data before export, without contacting Adobe or creating files.

Instructions

Preview up to 20 bounded MOGRT recipe exports from a workspace-contained JSON or CSV data file. It does not contact Adobe or create any compositions or files.

Input Schema

TableJSON Schema

Name	Required	Description
`brand_kit`	No	Optional validated brand-kit values applied to every batch recipe.
`data_file_path`	Yes	Existing workspace-contained .json or .csv file with recipe rows.
`output_directory`	Yes	Existing workspace-contained directory for every batch artifact.
`approved_workspace_path`	Yes	Absolute operator-approved workspace root.

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

Addedv1.14.9Sep 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real context the annotations do not: no Adobe contact occurs, no compositions or files are created, and the batch is capped at 20 rows.

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 sentences, no filler. The capability and its scope come first, followed by the non-effects clause, which is exactly the ordering an agent needs.

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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. The remaining gap is the absence of any pointer to preview_mogrt_recipe or create_mogrt_batch, which matters given how crowded the MOGRT sibling set is.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by disclosing the 20-item bound and reinforcing that both the data file and workspace are workspace-contained, which constrains how the three required path parameters should be supplied.

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 (MOGRT recipe exports), and scope (batch, up to 20, from a JSON/CSV data file). It is clearly distinguishable from create_mogrt_batch, though it never names preview_mogrt_recipe to clarify the single-vs-batch boundary.

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?

Usage is implied by 'from a workspace-contained JSON or CSV data file' — an agent can infer this is for reviewing a multi-row batch before exporting. However there is no explicit when-to-use / when-not, and no routing against the closely related preview_mogrt_recipe or create_mogrt_batch siblings.

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

Deploy Server