Premiere Pro MCP Server

Add Transition

add_transition

Insert a video transition at a cut point on a selected track by specifying the transition type, track index, and time position.

Instructions

Add a video transition between two clips at a cut point. Uses QE DOM.

Input Schema

TableJSON Schema

Name	Required	Description
`track_index`	Yes	Video track index (0-based)
`transition_name`	Yes	Name of the transition (e.g., 'Cross Dissolve', 'Dip to Black')
`duration_seconds`	No	Duration of the transition in seconds (default: 1.0)
`cut_point_seconds`	Yes	Time position in seconds of the cut point where the transition should be placed

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

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

B3.4/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-idempotent mutation, and the description adds little behavioral detail beyond that. The 'Uses QE DOM' note is an implementation detail rather than a useful behavior such as overwriting an existing transition or requiring handles around the cut.

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?

The description is short and front-loaded with the key action. The second sentence ('Uses QE DOM.') is an opaque implementation note that does not clearly earn its place but does not seriously harm clarity.

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

Completeness3/5

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

For a straightforward four-parameter tool with an output schema and annotations, the description is minimally sufficient. It is incomplete in that it never disambiguates from the similarly named add_transition_to_clip and gives no indication of prerequisites such as having an actual cut point.

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 parameters are already documented. The description adds only the contextual notion of placing a transition at a cut point, which does not materially extend the schema's meaning.

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?

The description uses a specific verb ('Add'), a clear object ('video transition'), and precise placement ('between two clips at a cut point'), so the core purpose is evident. It does not explicitly contrast with the similarly named sibling add_transition_to_clip, so sibling differentiation is incomplete.

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?

The description implies the tool is for applying transitions at cuts, which gives a general context for use. However, it provides no explicit guidance on when to prefer this tool over add_transition_to_clip or batch_add_transitions, or what conditions would make it unsuitable.

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

Deploy Server