Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_add_transitions

Add the same transition to every clip boundary on a Premiere Pro video track, applying consistent cross dissolves or other effects across all edits in one pass.

Instructions

Adds a transition to all clip boundaries on a track. Useful for quickly adding cross dissolves or other transitions between every clip.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sequenceId": "<sequenceId>",
      "trackIndex": "<trackIndex>",
      "transitionName": "<transitionName>",
      "duration": "<duration>"
    },
    "name": "batch_add_transitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationYesThe duration of each transition in seconds
sequenceIdYesThe ID of the sequence
trackIndexYesThe video track index (0-based)
transitionNameYesThe name of the transition (e.g., "Cross Dissolve")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It states the bulk mutation scope but does not disclose whether existing transitions are overwritten, whether clips are trimmed to make handles, whether audio tracks are supported, or what happens on failure. These are significant side effects for a bulk timeline operation.

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?

The description is two sentences, front-loaded with the action and scope, and contains no filler. It conveys the operation and use case efficiently.

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

Completeness2/5

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

For a bulk mutation with no annotations and no output schema, the description is too thin. It doesn't explain return behavior, overwrite/conflict handling, or whether it applies to video/audio/graphics tracks, leaving the agent uncertain about important preconditions and consequences.

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 every parameter has a clear description (e.g., 'duration in seconds', 'video track index (0-based)'). The tool description adds only an example transition name ('Cross Dissolve'), so it provides no meaningful extra parameter semantics beyond the schema.

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?

'Adds a transition to all clip boundaries on a track' uses a specific verb and resource, clearly differentiating it from single-boundary tools like add_transition. The phrase 'all clip boundaries' and 'between every clip' make the batch scope unambiguous.

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?

The description states it is 'useful for quickly adding cross dissolves or other transitions between every clip,' which implies the intended batch scenario. It doesn't explicitly exclude single-boundary use or mention add_transition as an alternative, but the context is clear enough.

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

Deploy Server

Other Tools