Adobe Premiere Pro MCP

Overview Schema Source Related Servers Discussions Admin

import_mogrt

Import a Motion Graphics Template (.mogrt) into a Premiere Pro sequence at a specified time, with optional track indices for placement.

Instructions

Imports a Motion Graphics Template (.mogrt) file into a sequence.

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": {
      "sequenceId": "<sequenceId>",
      "mogrtPath": "<mogrtPath>",
      "time": "<time>"
    },
    "name": "import_mogrt"
  }
}

Input Schema

Name	Required	Description
`time`	Yes	The time in seconds where the MOGRT should be placed
`mogrtPath`	Yes	The absolute path to the .mogrt file
`sequenceId`	Yes	The ID of the sequence
`audioTrackIndex`	No	The audio track index (default: 0)
`videoTrackIndex`	No	The video track index (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must disclose side effects but only states 'imports,' which implies a mutation. It does not mention whether existing clips are shifted, if the template replaces anything, or failure modes. Minimal behavioral disclosure.

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?

A single, focused sentence with no redundant information. It is front-loaded with the core action and destination, making it perfectly concise for a simple import tool.

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

Completeness2/5

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

For a tool that modifies a sequence, the description lacks crucial behavioral context (e.g., track placement behavior, effect on existing clips, error handling). No output schema or annotations exist to compensate. It is too sparse for a mutation operation.

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% with clear parameter descriptions. The description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate—adequate but not enriching.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('imports'), the resource ('.mogrt file'), and the destination ('into a sequence'). It distinguishes from the sibling tool 'import_mogrt_from_library' by specifying file path import, making the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'import_mogrt_from_library' or 'import_media'. It lacks preconditions (e.g., open sequence, track availability) and exclusion criteria, leaving usage context unclear.

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

Deploy Server