Skip to main content
Glama

add_transition_to_clip

Apply a video transition to the start or end of a clip in Adobe Premiere Pro. Specify clip ID, transition type, position, and duration to enhance editing workflow.

Instructions

Adds a transition to the beginning or end of a single clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIdYesThe ID of the clip
transitionNameYesThe name of the transition
positionYesWhether to add the transition at the start or end of the clip
durationYesThe duration of the transition in seconds

Implementation Reference

  • Executes the tool by generating and running an ExtendScript in Premiere Pro to add a transition to the specified position (start or end) of a clip on the timeline.
    private async addTransitionToClip(clipId: string, transitionName: string, position: 'start' | 'end', duration: number): Promise<any> {
      const script = `
        try {
          var clip = app.project.getClipByID("${clipId}");
          if (!clip) {
            JSON.stringify({
              success: false,
              error: "Clip not found"
            });
            return;
          }
          
          var track = clip.getTrack();
          var transition;
          
          if ("${position}" === "start") {
            transition = track.addTransition("${transitionName}", clip, "start", ${duration});
          } else {
            transition = track.addTransition("${transitionName}", clip, "end", ${duration});
          }
          
          if (!transition) {
            JSON.stringify({
              success: false,
              error: "Failed to add transition"
            });
            return;
          }
          
          JSON.stringify({
            success: true,
            message: "Transition added successfully",
            transitionName: "${transitionName}",
            position: "${position}",
            duration: ${duration},
            clipId: "${clipId}",
            transitionId: transition.nodeId
          });
        } catch (e) {
          JSON.stringify({
            success: false,
            error: e.toString()
          });
        }
      `;
      
      return await this.bridge.executeScript(script);
  • Zod schema defining the input parameters for the 'add_transition_to_clip' tool.
      name: 'add_transition_to_clip',
      description: 'Adds a transition to the beginning or end of a single clip.',
      inputSchema: z.object({
        clipId: z.string().describe('The ID of the clip'),
        transitionName: z.string().describe('The name of the transition'),
        position: z.enum(['start', 'end']).describe('Whether to add the transition at the start or end of the clip'),
        duration: z.number().describe('The duration of the transition in seconds')
      })
    },
  • Tool dispatch in the executeTool method's switch statement, mapping the tool name to its handler function.
    case 'add_transition_to_clip':
      return await this.addTransitionToClip(args.clipId, args.transitionName, args.position, args.duration);
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose whether this is destructive (modifies clip permanently), requires specific project states, has side effects, or how failures are handled. Minimal behavioral context beyond the core 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?

Single sentence, front-loaded with the core action, zero wasted words. Efficiently communicates the essential purpose without redundancy or fluff.

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 mutation tool with no annotations and no output schema, the description is inadequate. It lacks information about return values, error conditions, permissions, or how the transition integrates with the clip (e.g., overwrites existing transitions). Should provide more context given the tool's complexity.

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 parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying 'clipId' targets a single clip and 'position' has two options. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the action ('adds a transition') and target resource ('to a single clip'), specifying scope ('beginning or end'). It distinguishes from generic 'add_transition' by focusing on clip-level application, though not explicitly contrasting with all siblings.

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 guidance on when to use this tool versus alternatives like 'add_transition' (which might apply to sequences) or other clip-modification tools. The description implies usage for single clips but lacks context about prerequisites, timing, or workflow integration.

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/hetpatel-11/Adobe_Premiere_Pro_MCP'

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