Premiere Pro MCP Server

Set Target Track

set_target_track

Designate a video or audio track as the active target for insert and overwrite edits. Set targeted to true/false to select or release a track, keeping only one video and one audio track active.

Instructions

Set a track as targeted (active for insert/overwrite edits). Only one video and one audio track can be targeted at a time.

Input Schema

TableJSON Schema

Name	Required	Description
`targeted`	Yes	Whether to target (true) or untarget (false) the track
`track_type`	Yes	Track type
`track_index`	Yes	Track index (0-based)

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

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description carries the burden of behavioral context. It adds two genuinely useful traits: the functional consequence (active for insert/overwrite edits) and the exclusivity constraint (one video + one audio maximum). This goes beyond what any annotation or schema field states.

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, zero filler. The first sentence front-loads the operation and defines its meaning; the second adds the binding constraint. Every word earns its place.

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?

For a simple 3-param setter with an output schema and annotations intact, the description is nearly complete. The return value is covered by the output schema, and the key runtime constraint is disclosed. The only minor gap is that it doesn't explicitly state that targeting a new video track implicitly untargets the previously targeted one, though the stated constraint makes this inferable.

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 description coverage is 100%, so the baseline is 3. The description adds value by enriching the meaning of the 'targeted' parameter — clarifying that setting it true makes the track active for insert/overwrite edits — and by giving the two targeted parameters operational context through the one-per-type rule. This exceeds the schema's terse 'Whether to target (true) or untarget (false) the track'.

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?

States a specific verb (Set) and resource (track) with a precise semantic state: 'targeted (active for insert/overwrite edits)'. The parenthetical defines what 'targeted' means, and the singular 'a track' plus the one-per-type constraint implicitly distinguish it from siblings like set_all_tracks_targeted.

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 provides clear operational context — 'Only one video and one audio track can be targeted at a time' — which implies when to use targeted=false (before targeting a new track of the same type). However, it never explicitly names alternatives or states when-not-to-use it versus set_all_tracks_targeted, so usage guidance remains implied rather than stated.

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

Deploy Server