Premiere Pro MCP Server

Create Caption Track

create_caption_track

Import a reviewed caption artifact (SRT/VTT) into the active Premiere sequence, or generate a local timing/review plan for lecture captions.

Instructions

Import an already reviewed caption artifact into the active sequence, or create a local lecture-caption timing and review workflow plan. Import reports structural success only when the host exposes a caption-track readback; the planning action never contacts Premiere or changes an artifact.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	No	Use import (the default) to create a Premiere caption track, or plan_lecture_workflow for a read-only SRT/VTT timing and review plan.	import
`item_id`	No	For action import, the node ID or name of the imported caption project item (for example, an SRT file). Omit for plan_lecture_workflow.
`start_seconds`	No	For action import, offset in seconds from the start of the sequence (default: 0).
`caption_format`	No	For action import, Premiere caption format: subtitle (default), 608, 708, teletext, ebu, op42, or op47.
`artifact_format`	No	For plan_lecture_workflow, the syntax of caption_content. VTT content must include its WEBVTT header.
`caption_content`	No	For plan_lecture_workflow, the caller-owned SRT or VTT content to parse locally. The returned plan contains no caption text and does not write this artifact.
`observed_offset_seconds`	No	For plan_lecture_workflow, an editor-observed constant offset in seconds. Positive means captions currently appear later than intended; the preview proposes the inverse shift when safe.
`target_duration_seconds`	No	For plan_lecture_workflow, optional intended sequence duration. A mismatch requires review unless proportional scaling is explicitly authorized.
`timing_tolerance_seconds`	No	For plan_lecture_workflow, tolerance used to classify an offset or duration mismatch (default: 0.25 seconds).
`allow_proportional_scaling`	No	For plan_lecture_workflow, explicitly permit a bounded timing-scale preview when the artifact end does not match target_duration_seconds. This still never rewrites a caption artifact.

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.18.6Sep 30, 2026

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

Changed15 schema fields changedv1.14.9Sep 8, 2026

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

addedInput schema / properties / action

Added value: +{
+  "default": "import",
+  "description": "Use import (the default) to create a Premiere caption track, or plan_lecture_workflow for a read-only SRT/VTT timing and review plan.",
+  "enum": [
+    "import",
+    "plan_lecture_workflow"
+  ],
+  "type": "string"
+}

addedInput schema / properties / allow_proportional_scaling

Added value: +{
+  "description": "For plan_lecture_workflow, explicitly permit a bounded timing-scale preview when the artifact end does not match target_duration_seconds. This still never rewrites a caption artifact.",
+  "type": "boolean"
+}

addedInput schema / properties / artifact_format

Added value: +{
+  "description": "For plan_lecture_workflow, the syntax of caption_content. VTT content must include its WEBVTT header.",
+  "enum": [
+    "srt",
+    "vtt"
+  ],
+  "type": "string"
+}

addedInput schema / properties / caption_content

Added value: +{
+  "description": "For plan_lecture_workflow, the caller-owned SRT or VTT content to parse locally. The returned plan contains no caption text and does not write this artifact.",
+  "maxLength": 750000,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / caption_format / description

Previous value: -"Caption format: 'subtitle' (default), '608', '708', 'teletext', 'ebu', 'op42', 'op47'"New value: +"For action import, Premiere caption format: subtitle (default), 608, 708, teletext, ebu, op42, or op47."

changedInput schema / properties / item_id / description

Previous value: -"Node ID or name of the imported caption project item (e.g., an .srt file)"New value: +"For action import, the node ID or name of the imported caption project item (for example, an SRT file). Omit for plan_lecture_workflow."

addedInput schema / properties / item_id / maxLength
```
Added value: +512
```

addedInput schema / properties / observed_offset_seconds

Added value: +{
+  "description": "For plan_lecture_workflow, an editor-observed constant offset in seconds. Positive means captions currently appear later than intended; the preview proposes the inverse shift when safe.",
+  "maximum": 86400,
+  "minimum": -86400,
+  "type": "number"
+}

changedInput schema / properties / start_seconds / description

Previous value: -"Offset in seconds from the start of the sequence (default: 0)"New value: +"For action import, offset in seconds from the start of the sequence (default: 0)."

addedInput schema / properties / start_seconds / maximum
```
Added value: +604800
```
addedInput schema / properties / start_seconds / minimum
```
Added value: +0
```

addedInput schema / properties / target_duration_seconds

Added value: +{
+  "description": "For plan_lecture_workflow, optional intended sequence duration. A mismatch requires review unless proportional scaling is explicitly authorized.",
+  "maximum": 604800,
+  "minimum": 0.001,
+  "type": "number"
+}

addedInput schema / properties / timing_tolerance_seconds

Added value: +{
+  "description": "For plan_lecture_workflow, tolerance used to classify an offset or duration mismatch (default: 0.25 seconds).",
+  "maximum": 10,
+  "minimum": 0.001,
+  "type": "number"
+}

removedInput schema / required
```
Removed value: -[
-  "item_id"
-]
```

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

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, but not which action mutates. The description adds real value by disclosing that import reports structural success only when the host exposes a caption-track readback, and that plan_lecture_workflow never contacts Premiere or changes an artifact. This per-action behavioral split is not derivable from the tool-level annotations.

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?

Two dense sentences, front-loaded with the dual purpose and followed by the behavioral caveat. Every clause carries information, though the second sentence is somewhat long and packs two distinct behavioral points.

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 not be explained. For a 10-parameter tool with no required params, the description covers both modes, their side-effect profiles, and the success semantics of import. It stops short of explaining how the plan output should be reviewed, but the core is complete.

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% and each parameter, including the two enums, is documented in the schema itself. The description adds no syntax or format detail beyond what the schema already provides, so the baseline of 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?

The description states two specific verbs and resources: importing a reviewed caption artifact into the active sequence, and creating a local lecture-caption timing/review plan. That is clear and far from a restatement of the name. It falls short of 5 because it never names or distinguishes against caption siblings like build_caption_artifact or read_sequence_captions.

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 phrase 'already reviewed caption artifact' implies a prerequisite for the import path, and the two actions imply their own use contexts. However, there is no explicit when-to-use versus build_caption_artifact or read_sequence_captions, and no stated exclusions, so the routing guidance is only implied.

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

Deploy Server