Premiere Pro MCP Server

Verify Temporal Render Artifact

verify_temporal_render_artifact

Read-onlyIdempotent

Validates short exported video samples against expected RGB tolerances and optional decoded-audio RMS windows, rejecting stills or mismatched artifacts while recording hashes and host provenance.

Instructions

Validate actual short exported video at 2–32 times with decoded RGB tolerances and optional decoded-audio RMS windows. Rejects stills and mismatched samples; records fixture/artifact hashes and explicit declared host provenance. This sampled harness does not prove all frames, Undo/reopen, playback, glyphs or destination compatibility.

Input Schema

Name	Required	Description
`host`	No	Optional caller-declared licensed-host provenance; artifact analysis cannot authenticate these values.
`path`	Yes	Absolute existing caller-selected video artifact (maximum 1 GiB, expected duration at most 60 seconds).
`samples`	Yes	Expected temporal image checks; choose times around transitions and interpolation, with compression-aware tolerances.
`fixture_id`	Yes	Opaque fixture ID.
`audio_samples`	No	Optional actual decoded-audio energy checks; analysis downmixes to mono 48kHz and cannot prove multichannel routing.
`fixture_sha256`	Yes	Lowercase SHA-256 of generated fixture/input definition.
`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 one HTTP session) 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`	Yes	Expected actual video duration.
`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.
`duration_tolerance_seconds`	No	Allowed duration deviation, default 0.05 seconds.

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.

Changed2 schema fields changedv1.25.0Oct 24, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "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 one HTTP session) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}

addedOutput schema / properties / idempotency

Added value: +{
+  "additionalProperties": true,
+  "description": "Present when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.",
+  "type": "object"
+}

Addedv1.24.0Oct 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/no-destroy annotations, it discloses rejection behavior, that fixture/artifact hashes and declared host provenance are recorded (and that host values are unauthenticated structural provenance), and an explicit sampling-coverage disclaimer. That is unusually rich behavioral context for a read-only verification tool.

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 dense sentences, front-loaded with the action and oracle type, then validation rejects, then scope limits. Every sentence earns its place; only the compressed phrase "at 2–32 times" is slightly ambiguous versus "2–32 sample points".

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

Completeness5/5

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

With an output schema present, the description needn't explain return values, and the 11-parameter schema is fully documented. The description still covers the essential gaps: input preconditions, sampled nature, provenance recording, and what the result does not certify.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning: the 2–32 sample-time range (mapping to samples minItems/maxItems) and the optional audio-window mode, which the schema only exposes field-by-field. "Short" also justifies the 60s/1 GiB bounds.

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?

Specific verb + resource: "Validate actual short exported video" via decoded RGB tolerances and optional audio RMS windows. The sampled-oracle framing plus "Rejects stills" clearly separates it from stills/scope/delivery-conformance siblings without naming them explicitly.

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?

"Rejects stills and mismatched samples" and the closing "does not prove all frames, Undo/reopen, playback, glyphs or destination compatibility" give concrete when-not boundaries that steer the agent away from using this as a full delivery proof. No sibling alternative is named, so it stops short of a 5.

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

Deploy Server