premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Export Job Status

get_export_job_status

Read-onlyIdempotent

Read an export job's status by job ID—queued, encoding progress, completed, failed, or cancelled—without starting, cancelling, or retrying renders.

Instructions

Read the status of an export job started by export_sequence_job_start: queued, encoding (with AME-reported progress when events arrive), finalizing, completed, failed, cancelled, or unknown. Evidence is reported separately: Adobe Media Encoder job events recorded inside Premiere's ExtendScript engine, and Node-side observation of the output file (exists, non-empty, size and modification time unchanged across stability_window_ms and since the previous poll). completed is verified only when AME reported completion, the file is stable and non-empty, and ffprobe confirms its duration within one frame; without an AME completion event a stable file is reported as completed but unverified. Jobs started by an earlier server process report unknown (server_restarted). Read-only: it never starts, cancels, or retries a render.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_export_job_status"
  }
}

Input Schema

Name	Required	Description
`job_id`	Yes	jobId returned by export_sequence_job_start
`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.
`stability_window_ms`	No	How long to wait between the two output-file size checks in this call (default 2000 ms)
`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

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds substantial non-obvious behavior: the two separate evidence channels (AME events vs Node-side file observation), the exact conditions for a *verified* completed status, the degraded 'completed but unverified' outcome when no AME completion event exists, and the server_restarted → unknown case.

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?

Front-loads the status enumeration and follows with verification logic, so an agent reads the most decision-relevant facts first. The single dense paragraph is long and the evidence-channel sentence is information-dense, but nearly every clause carries distinct behavior rather than filler.

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?

Despite an output schema existing, the description supplies the interpretive layer an agent needs to read results correctly: how completed is verified, when it is only provisional, and why unknown appears. Nothing material about polling or status interpretation is left unexplained for this 5-parameter tool.

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 100%, so the baseline is 3; the description earns above that by explaining what stability_window_ms actually does in this tool's logic (size/modification time unchanged across the window and since the previous poll), giving the parameter operational meaning rather than restating it.

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?

States a specific verb and resource ('Read the status of an export job started by export_sequence_job_start') and enumerates the exact status vocabulary (queued, encoding, finalizing, completed, failed, cancelled, unknown), which lets an agent distinguish it from siblings like get_render_queue_status or inspect_workflow_job without opening schemas.

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?

Ties itself explicitly to the job created by export_sequence_job_start and closes with 'Read-only: it never starts, cancels, or retries a render,' which rules out misuse for cancellation. It does not name the sibling an agent should use to cancel or retry, so the routing is clear on the negative side but not fully on the positive side.

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

Deploy Server