premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Create Mogrt Recipe

create_mogrt_recipe

Save exactly one previewed MOGRT recipe to an existing After Effects project after explicit export confirmation; it does not create projects or output folders.

Instructions

Create exactly one previewed MOGRT recipe in a saved After Effects project inside the approved workspace. Requires explicit export confirmation; it never creates projects or output folders.

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_export": "<confirm_export>"
    },
    "name": "create_mogrt_recipe"
  }
}

Input Schema

Name	Required	Description
`preview_token`	Yes	One-time token returned by preview_mogrt_recipe; it expires after 10 minutes.
`confirm_export`	Yes	Must be true to save the open AE project and request the planned .mogrt export.
`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

A3.8/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the base bar is lower. The description adds real context: a mandatory confirmation gate and the fact that it will not create projects or output folders. It omits the retry/idempotency behavior (schema-level idempotency_key, replay semantics) and the session-scoped dedup limits that matter for a mutation call.

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 compact sentences with zero filler; the core action and cardinality lead, and the confirmation constraint and exclusions follow. Everything in it is load-bearing.

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?

Output schema exists, so return values need not be explained, and the description covers scope, preconditions and exclusions for a nested-schema mutation tool. The remaining gap is that it does not surface the idempotency/retry contract or the preview-token expiry that govern how the call should be issued and re-issued.

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 coverage is 100%, so the schema carries parameter documentation and baseline 3 applies. The description adds semantic framing by implying both required parameters ("previewed" → preview_token, "explicit export confirmation" → confirm_export) but does not mention idempotency_key or the optional expected_* guards, which are the most error-prone inputs.

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 and resource ("Create exactly one previewed MOGRT recipe"), plus scope ("exactly one") and target ("a saved After Effects project inside the approved workspace"). The cardinality wording implicitly separates it from the batch sibling create_mogrt_batch, though no sibling is named directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the export-confirmation precondition explicit and adds negative guidance ("it never creates projects or output folders"), which steers agents away from create_project-style tools. It stops short of naming preview_mogrt_recipe as the required prerequisite, even though the preview_token dependency makes that the natural pairing.

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

Deploy Server