premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Import Mogrt

import_mogrt

Imports a .mogrt Motion Graphics Template onto a timeline track at a given start time and duration, then writes each text control explicitly and reads it back to confirm the final values.

Instructions

Import a Motion Graphics Template (.mogrt) file and add it to the timeline. Pass text_values (for example { "Headline": "..." }) to write each text control explicitly after insertion and verify it by readback, so a template default or stale value is never left in place silently. Placement fields contain observed start/end/track values; requested values are separate, and unreadable geometry remains committed_unverified.

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": {
      "mogrt_path": "<mogrt_path>"
    },
    "name": "import_mogrt"
  }
}

Input Schema

Name	Required	Description
`mogrt_path`	Yes	Full path to the .mogrt file
`text_values`	No	Optional map of MOGRT text parameter display names to the exact text to write (for example { "Headline": "Chapter 3" }). Each value is written explicitly after import and read back; the result reports verified, mismatch, missing_property, or committed_unverified per field.
`track_index`	No	Video track index (default: 0)
`start_seconds`	No	Start time in seconds (default: 0)
`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.
`duration_seconds`	No	Duration in seconds (default: 5). Applied after import by moving the graphic's end and read back; a duration that would overlap the next clip on the track is not applied.
`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

Behavior4/5

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

Annotations only declare the generic safety profile (readOnlyHint false, destructiveHint false, idempotentHint false), so the description carries real weight here and delivers: text values are written explicitly after insertion and verified by readback, with per-field outcomes. It also discloses the failure/edge behavior that placement fields hold observed start/end/track values while requested values are separate, and that unreadable geometry stays committed_unverified — genuinely useful state semantics not present in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and then the highest-risk detail (silent stale text values). The middle sentence is long and packs verification states into a subordinate clause, but no sentence is filler.

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 mutation tool with 8 parameters, nested guard objects, and an output schema, the description covers purpose, the risky text-write path, and the unverified-geometry outcome. The bulky guard parameters (expected_cep_target, expected_project_path) and idempotency behavior are only in the schema, which is acceptable given full coverage and a declared output schema.

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 description coverage is already 100%, so the baseline would be 3; the description adds meaning on top by explaining the intent of text_values with a concrete example and by clarifying the observed-vs-requested distinction for the placement fields (start/track). It says nothing about the idempotency key or the expected_cep_target/expected_project_path guards, but those are thoroughly documented in 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 opens with a specific verb and resource: 'Import a Motion Graphics Template (.mogrt) file and add it to the timeline', which is concrete and immediately actionable. It does not, however, distinguish itself from the obvious sibling import_mogrt_from_library, so an agent must infer the difference from the sibling's name alone.

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?

It gives clear in-tool guidance about passing text_values so template defaults are never silently left in place, which is a strong procedural hint. But it offers no explicit when-to-use / when-not-to-use framing relative to alternatives such as import_mogrt_from_library or import_ae_comps, leaving selection between import paths implied.

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

Deploy Server