premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Inspect After Effects Render Templates

inspect_after_effects_render_templates

Idempotent

Reads available After Effects render and output-module template names from the first render-queue item, temporarily adding one when the queue is empty; never renders.

Instructions

Read available render and output-module template names from the first existing After Effects render-queue item. After Effects only exposes templates through a queue item, so on an empty queue pass allow_temporary_queue_item: true to add one composition to the queue, read the names and remove it again (requires edit; the queue length is read back unchanged). It never renders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_after_effects_render_templates"
  }
}

Input Schema

Name	Required	Description
`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.
`composition_name`	No	Composition to queue temporarily (default: the first composition in the project). Only used with allow_temporary_queue_item.
`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.
`allow_temporary_queue_item`	No	When the render queue is empty, briefly queue one composition to read template names, then remove it. Default false (read-only; refuses on an empty queue).

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

Behavior4/5

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

Adds real value beyond the annotations: readOnlyHint is false for an "inspect" tool, and the description explains exactly why (a temporary queue item is added, read, then removed) and reassures that queue length is read back unchanged and nothing renders. It stops short of stating what happens if the temporary item cannot be added or removed.

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, front-loaded with the purpose, then the empty-queue workaround with its cost and safety note. No filler and no restatement of the title.

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?

An output schema exists so return values need no explanation, and the description covers the one genuinely surprising behavior (temporary queue mutation). It omits prerequisites such as an open project or a live AE connection, which an agent may need before calling.

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 already 100%, so 3 is the floor. The description still adds meaning for the two AE-specific parameters by tying allow_temporary_queue_item to the empty-queue scenario and noting composition_name defaults to the first composition, though it says nothing about the idempotency_key or expected_* guard parameters.

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?

Opens with a specific verb and resource: "Read available render and output-module template names from the first existing After Effects render-queue item." The scope (first queue item only) plus "It never renders" separates it cleanly from the enqueue/preview siblings in the catalog.

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?

Gives an explicit conditional path: on an empty queue pass allow_temporary_queue_item: true. That is clear when-to-use context, but no alternative sibling is named for the case where the caller actually wants to render or inspect template source rather than names.

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

Deploy Server