Premiere Pro MCP Server

Add To Timeline Batch

add_to_timeline_batch

Insert up to 32 project items into a Premiere Pro timeline in one validated batch request. Preflights items and tracks, then verifies final placements to report any unverified changes.

Instructions

Insert up to 32 project items with insert-edit semantics in one validated CEP request. Experimental QE sync-lock handling may ripple or split earlier placements. The tool preflights items and tracks, then verifies every placement again in the final sequence; changed placements return committed_unverified with their observed final positions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`clips`	Yes	Ordered placements. They use the same insert-edit semantics as add_to_timeline; later placements must not share a target video-track start time.

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

Changed11 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- changedInput schema / properties / clips / items / additionalProperties
```
Previous value: -{}New value: +false
```
- addedInput schema / properties / clips / items / properties / audio_track_index / minimum
```
Added value: +0
```
- addedInput schema / properties / clips / items / properties / audio_track_index / type
```
Added value: +"integer"
```
- addedInput schema / properties / clips / items / properties / item_id / maxLength
```
Added value: +512
```
- addedInput schema / properties / clips / items / properties / item_id / minLength
```
Added value: +1
```
- addedInput schema / properties / clips / items / properties / start_seconds / minimum
```
Added value: +0
```
- addedInput schema / properties / clips / items / properties / track_index / minimum
```
Added value: +0
```
- addedInput schema / properties / clips / items / properties / track_index / type
```
Added value: +"integer"
```
- addedInput schema / properties / clips / maxItems
```
Added value: +32
```
- addedInput schema / properties / clips / minItems
```
Added value: +1
```
Addedv1.14.4Aug 29, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description discloses substantial behavior beyond the annotations: experimental QE sync-lock handling may ripple or split earlier placements, the tool preflights items and tracks, and it verifies placements in the final sequence. It also explains that changed placements return 'committed_unverified' with observed final positions.

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 three sentences and front-loads the core purpose before caveats and verification behavior. Each sentence earns its place, though the final sentence is dense and could be slightly more scannable.

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

Completeness5/5

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

For a complex batch-edit tool with an output schema and annotations covering safety, the description provides the key operational caveats: experimental sync-lock ripple/split behavior, preflight validation, final verification, and the committed_unverified status. Nothing critical for correct invocation appears to be missing.

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 baseline is 3. The description reinforces 'up to 32 project items' and 'insert-edit semantics,' but adds no parameter-level detail beyond what the schema already documents for the clips array.

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?

The description states a specific verb and resource with scope: 'Insert up to 32 project items with insert-edit semantics in one validated CEP request.' It immediately distinguishes the tool as a batch operation limited to 32 items, setting it apart from single-item siblings such as add_to_timeline.

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?

Usage is implied by the batch scope and 'insert-edit semantics,' but the description never explicitly says when to choose this tool over add_to_timeline or other insertion tools. No when-not or alternative guidance is provided.

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

Deploy Server