Skip to main content
Glama
Siddhant704

Premiere Pro MCP Server

by Siddhant704

apply_transition

Apply a named video or audio transition to a specific clip edge on a Premiere Pro timeline, with control over duration and sequence.

Instructions

Apply a video transition (by name) to a clip edge on the timeline. Requires Premiere's QE DOM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIndexYes
trackTypeYes
trackIndexYes
sequenceNameNo
transitionNameYese.g. 'Cross Dissolve', 'Dip to Black'
durationSecondsNo
Behavior3/5

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

Mentions dependency on Premiere's QE DOM and applies to clip edge, but does not clarify which edge (in/out), error behavior, or side effects. No annotations present to supplement.

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 concise sentences, front-loaded with core purpose and essential prerequisite. No wasted words.

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?

Description omits critical details: which clip edge, return behavior, error handling, and no output schema. For a tool with 6 parameters and mutation side-effects, this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (17%), and description adds minimal parameter context (only transitionName examples). Most parameters like clipIndex, trackIndex lack semantics.

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?

Description clearly states verb 'apply', resource 'video transition (by name)' and target 'clip edge on the timeline'. Differentiates from sibling 'apply_effect' by specifying transition vs effect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives like 'apply_effect'. No exclusion criteria or prerequisites beyond the brief mention of QE DOM.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Siddhant704/premiere-pro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server