Skip to main content
Glama

Preview Mogrt Recipe

preview_mogrt_recipe
Read-onlyIdempotent

Preview a bounded MOGRT recipe from built-in title, callout, quote, social, and media-placeholder templates. Validates an existing workspace output directory without contacting Adobe or writing files.

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.

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": {
      "template_name": "<template_name>",
      "headline": "<headline>",
      "approved_workspace_path": "<approved_workspace_path>",
      "output_directory": "<output_directory>"
    },
    "name": "preview_mogrt_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthNoComposition width from 320 to 7680 pixels; defaults to 1920.
heightNoComposition height from 240 to 4320 pixels; defaults to 1080.
recipeNoSupported authored template recipe; defaults to lower_third.
headlineYesPrimary headline text, at most 160 characters. Required for text recipes; optional caption for media_placeholder.
subtitleNoOptional secondary lower-third text, at most 160 characters.
brand_kitNoOptional 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_rateNoComposition frame rate; defaults to 30.
text_colorNoOptional text color as #RRGGBB; defaults to #FFFFFF.
accent_colorNoOptional accent fill color as #RRGGBB; defaults to #2563EB.
template_nameYesSafe template file stem; the generated artifact is template_name.mogrt.
text_controlsNofull (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.
idempotency_keyNoOptional 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.
duration_secondsNoComposition duration between 2 and 30 seconds; defaults to 5.
output_directoryYesExisting absolute output directory inside approved_workspace_path; this workflow never creates directories.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional 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.
placeholder_media_pathNoRequired for media_placeholder: absolute workspace-contained PNG, JPEG, MOV, or MP4 placed as the swappable Essential Graphics media slot.
approved_workspace_pathYesAbsolute operator-approved workspace root containing the saved AE project and output directory.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent 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.

  1. First observedv1.30.0

TDQS

A3.7/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 description is not carrying the safety burden alone. It still adds real context beyond them: it validates exactly one existing output directory and explicitly does not contact Adobe or write files, which is the key behavioral fact an agent needs before invoking a 'preview'.

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, zero filler, with the resource and scope front-loaded and the non-mutating guarantee placed last as the operative caveat. Nothing repeats the name or the annotations verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 18 parameters, nested objects, an output schema and strong annotations, much is already carried by structured fields, so the short description is defensible. However, for a preview tool in a catalog that also contains delete_preview_files and preview_mogrt_library_publish, the description says nothing about the preview artifact's lifecycle, where it lands, or how it is cleaned up.

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%, including long-form notes on idempotency_key, text_controls, expected_cep_target and placeholder_media_path, so the baseline is 3. The description's only parameter-adjacent contribution is that output_directory must already exist and that no directories are created, which is marginal on top of 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 names a specific verb ('Preview') and resource ('a bounded After Effects MOGRT recipe') and scopes it to the supported template library (title, callout, quote, social, media-placeholder), which aligns with the recipe enum. It is clearly distinguishable from create_mogrt_recipe by verb alone, though it never names a sibling explicitly.

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 rather than stated: 'preview' plus 'does not contact Adobe or write any files' tells an agent this is the safe dry-run step before generation, but it never says when to prefer it over create_mogrt_recipe or preview_mogrt_batch, nor what prerequisites (saved AE project, approved workspace) gate the call.

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

Deploy Server

Other Tools