premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Verify Mogrt Artifact

verify_mogrt_artifact

Read-onlyIdempotent

Confirms a workspace-contained .mogrt artifact exists locally and has a ZIP header, validating basic file presence before import.

Instructions

Verify that a workspace-contained .mogrt artifact exists locally and has a ZIP header. This does not prove controls, import compatibility, playback, or visual correctness.

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

Input Schema

Name	Required	Description
`mogrt_path`	Yes	Absolute .mogrt artifact path inside approved_workspace_path.
`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.
`approved_workspace_path`	Yes	Absolute operator-approved workspace root containing mogrt_path.

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

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's added value is in disclosing the exact scope of the check and its explicit limits — a rare and useful disclosure. It does not say what happens on failure (error vs. negative result), but the output schema plausibly carries the result shape.

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 affirmative scope front-loaded and the caveat immediately after. Every clause carries information an agent needs to decide whether to call this tool.

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 read-only verification tool with a full schema and an output schema, the description supplies exactly what structured fields cannot: what is actually proven versus not proven. The only minor gap is silence on whether the optional CEP/project-path guards affect a local-only check, which the schema addresses but the description does not reinforce.

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%, so the schema already documents all five parameters including the nested guard objects and the idempotency key. The description adds only the phrase 'workspace-contained' to reinforce that mogrt_path must sit under approved_workspace_path; it says nothing about the CEP/project-path guards, but with full schema coverage the baseline of 3 applies.

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 states a specific verb (Verify) and a precisely bounded resource (a workspace-contained .mogrt artifact), then enumerates the two exact checks performed: local existence and a ZIP header. That level of specificity distinguishes it from broader file/handoff verification siblings without needing to name them.

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?

The second sentence is an effective when-not-to-rely clause: 'This does not prove controls, import compatibility, playback, or visual correctness,' which steers an agent toward deeper validation tools when those guarantees are needed. It stops short of naming the specific alternative tools or stating a positive 'use this when' trigger, so it is clear context without full routing.

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

Deploy Server