premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Export Sequence Job Start

export_sequence_job_start

Start an asynchronous Adobe Media Encoder export of the active sequence and get a job ID immediately, so long renders don't block the MCP call. Poll get_export_job_status for completion.

Instructions

Start an asynchronous Adobe Media Encoder export of the active sequence and return a job id at once, so long renders (such as full episodes) do not hold the MCP call open. Poll get_export_job_status until it reports completed or failed. Requires a saved project, an .epr preset_path (Same as Project presets are refused), an existing output folder, and an output_path with no file yet (existing files are always refused; AME may otherwise rename or overwrite). The output extension must match the preset; a missing extension is added. range follows export_sequence: in_to_out and work_area fail closed instead of encoding the whole timeline. start_batch (default true) asks AME to start every ready queue job, including unrelated ones. Success means AME accepted the job (committed_unverified); render completion and the file are verified later by get_export_job_status. Jobs are tracked only by this server process.

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": {
      "output_path": "<output_path>",
      "preset_path": "<preset_path>"
    },
    "name": "export_sequence_job_start"
  }
}

Input Schema

Name	Required	Description
`range`	No	What to render: the entire sequence (default), the sequence in/out range, or an enabled work area around part of the sequence. Ranged modes are refused when they would encode the whole timeline.
`output_path`	Yes	Full output file path that does not exist yet, in an existing folder (e.g., '/Users/me/exports/episode-12.mp4')
`preset_path`	Yes	Required path to an Adobe Media Encoder preset file (.epr) with an explicit output location (not Same as Project)
`start_batch`	No	Ask Adobe Media Encoder to start its queue after queuing this job (default true). This starts every ready AME job, including unrelated ones. Pass false to only queue it; the job then stays queued until the AME queue is started (start_batch_encode).
`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.

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.7/5.0

Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-readonly, non-destructive, non-idempotent, non-open-world write): it discloses that success means only 'committed_unverified' acceptance by AME, that completion is verified later, that existing output files are always refused and 'Same as Project' presets are refused, that a missing extension is added and must match the preset, and that ranged modes 'fail closed'. It also flags a real side effect the annotations miss – start_batch=true starts every ready AME job including unrelated ones – and the session-scoped job tracking limit.

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?

Front-loads the action and return value in the first clause, then moves to polling guidance, then prerequisites, then edge cases. Every sentence carries operational information (refusal rules, side effects, success semantics); nothing is redundant with the title or annotations.

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?

For a 7-parameter, nested-schema, side-effecting async tool, the description covers the full lifecycle: preconditions, what acceptance means, how to verify, and the process-lifetime limitation on job tracking. An output schema exists, and the description appropriately does not restate return fields.

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; the description still adds meaning by stating the output extension must match the preset and that a missing extension is auto-added, plus the 'fail closed' behavior of in_to_out/work_area and the fact that start_batch starts unrelated jobs. It does not explain idempotency_key or expected_cep_target, but those are self-documented in the schema.

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?

Names a specific verb and resource ('Start an asynchronous Adobe Media Encoder export of the active sequence') and states the immediate return ('a job id at once'), which cleanly separates it from the sibling export_sequence (synchronous) and get_export_job_status (polling). The rationale for asynchrony ('long renders do not hold the MCP call open') further sharpens what this tool is for.

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?

Explicitly routes the agent to the follow-up tool ('Poll get_export_job_status until it reports completed or failed') and lists the preconditions that must hold before calling. It does not say when to prefer the synchronous export_sequence over this one, so the choice between siblings is only implied by the 'long renders' rationale rather than stated as a rule.

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

Deploy Server