Add To Render Queue

add_to_render_queue

Send the active sequence to Adobe Media Encoder's render queue for encoding. Requires a saved project and an .epr preset; optionally starts all ready jobs.

Instructions

Request an Adobe Media Encoder render-queue handoff for the active sequence. Requires a saved project and an .epr preset_path. Same as Project presets are refused before Premiere is contacted because AME encodes from a scratch project copy. Optional start_batch requests processing of every ready AME queue job, including unrelated jobs.

Input Schema

TableJSON Schema

Name	Required	Description
`output_path`	Yes	Full output file path
`preset_path`	Yes	Required path to an AME preset file (.epr). Omitting this raises an Illegal Parameter error on current Premiere hosts.
`start_batch`	No	Opt in to start the entire ready Adobe Media Encoder queue after this handoff, including unrelated jobs. Default false (enqueue only). A successful call does not verify that any render started or completed.

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.19.0Oct 3, 2026

addedInput schema / properties / start_batch

Added value: +{
+  "description": "Opt in to start the entire ready Adobe Media Encoder queue after this handoff, including unrelated jobs. Default false (enqueue only). A successful call does not verify that any render started or completed.",
+  "type": "boolean"
+}

Changed2 schema fields changedv1.18.6Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / properties / data / description

Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."

Changed2 schema fields changedv1.16.0Sep 16, 2026

changedInput schema / properties / preset_path / description

Previous value: -"Path to an AME preset file (.epr)"New value: +"Required path to an AME preset file (.epr). Omitting this raises an Illegal Parameter error on current Premiere hosts."

changedInput schema / required

Previous value: -[
-  "output_path"
-]New value: +[
+  "output_path",
+  "preset_path"
+]

Changed2 schema fields changedv1.14.4Aug 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Adds real behavioral context beyond the annotations: Project presets are refused before Premiere is contacted, AME encodes from a scratch project copy, and start_batch triggers every ready AME job including unrelated ones. This is meaningful disclosure for a non-idempotent, non-destructive mutation, though it does not cover auth or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the whole thing is short. However the sentence 'Same as Project presets are refused before Premiere is contacted' is garbled and reads like a broken copy-paste, hurting clarity despite the brevity.

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?

With annotations, a 100%-covered schema, and an output schema present, the description supplies the key gotchas an agent needs (saved project requirement, .epr preset prerequisite, scratch-copy behavior, batch side effect). It is nearly complete, missing only explicit sibling routing.

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 output_path, preset_path, and start_batch. The description reinforces preset_path and start_batch semantics but adds little that the schema does not already state, so the baseline 3 is appropriate.

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?

States a specific verb+resource: requesting an Adobe Media Encoder render-queue handoff for the active sequence. An agent understands exactly what the tool does. It does not explicitly differentiate from siblings like start_batch_encode or encode_project_item, so it stops short of a 5.

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

Usage Guidelines3/5

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

Provides prerequisites (saved project, .epr preset_path) and explains the start_batch opt-in, which implies when to use the flag. However it never names an alternative tool or states when NOT to use this versus start_batch_encode or encode_project_item, so guidance is implied rather than explicit.

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

Deploy Server

Premiere Pro MCP Server