Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_transition

Add a cross dissolve or other transition between two adjacent timeline clips by specifying both clip IDs, transition name, and duration.

Instructions

Adds a transition (e.g., cross dissolve) between two adjacent clips on the timeline.

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": {
      "clipId1": "<clipId1>",
      "clipId2": "<clipId2>",
      "transitionName": "<transitionName>",
      "duration": "<duration>"
    },
    "name": "add_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipId1YesThe ID of the first clip (outgoing)
clipId2YesThe ID of the second clip (incoming)
durationYesThe duration of the transition in seconds
transitionNameYesThe name of the transition to add (e.g., "Cross Dissolve")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided so the description must carry full transparency burden. It describes adding a transition which modifies the timeline between two clips, but does not disclose potential effects such as whether it replaces an existing transition, whether both clips need to be selected, or any timeline restriction.

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?

Single sentence that directly states the action, object, and position; no repetition or filler; concise and front-loaded.

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?

All four required parameters are specified with types and descriptions, covering fully the inputs for the operation. No output schema exists, but the description's expected timeline modification is clear enough; not penalizing heavily.

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 coverage is 100% and each parameter includes a clear description (IDs, duration in seconds, and transition name). Description adds no additional semantics beyond the schema for transitionName (example Cross Dissolve). Baseline 3.

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?

Description states a specific verb ('Adds') and resource ('transition') and identifies the location ('between two adjacent clips on the timeline'), fairly distinguishing this from sibling tools that list available transitions. However, it doesn't explicitly name alternatives when a specific transition is unavailable.

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?

The description implies when this tool is used (adding a transition between adjacent clips) but lacks explicit alternatives or exclusion guidance, such as checking available transitions first via list_available_transitions.

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