Skip to main content
Glama

remove_from_timeline

Remove clips from your Premiere Pro timeline with options to ripple delete (close gaps) or lift (leave gaps). This tool helps streamline video editing workflows by eliminating unwanted footage directly from the timeline.

Instructions

Removes a clip from the timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIdYesThe ID of the clip on the timeline to remove
deleteModeNoWhether to ripple delete (close gap) or lift (leave gap)

Implementation Reference

  • The core handler function for the 'remove_from_timeline' tool. It constructs and executes an ExtendScript via the PremiereProBridge to locate the clip by ID on the active sequence timeline and remove it using either 'ripple' (closes gap) or 'lift' (leaves gap) mode.
    private async removeFromTimeline(clipId: string, deleteMode = 'ripple'): Promise<any> {
      const script = `
        try {
          var clip = app.project.getClipByID("${clipId}");
          if (!clip) {
            JSON.stringify({
              success: false,
              error: "Clip not found"
            });
            return;
          }
          
          var clipName = clip.name;
          var track = clip.getTrack();
          
          if ("${deleteMode}" === "ripple") {
            track.removeClip(clip, true); // ripple delete
          } else {
            track.removeClip(clip, false); // lift delete
          }
          
          JSON.stringify({
            success: true,
            message: "Clip removed from timeline",
            clipId: "${clipId}",
            clipName: clipName,
            deleteMode: "${deleteMode}"
          });
        } catch (e) {
          JSON.stringify({
            success: false,
            error: e.toString()
          });
        }
      `;
      
      return await this.bridge.executeScript(script);
    }
  • Zod input schema defining parameters for the tool: clipId (required string) and optional deleteMode (enum: 'ripple' or 'lift'). Used for validation in executeTool.
    inputSchema: z.object({
      clipId: z.string().describe('The ID of the clip on the timeline to remove'),
      deleteMode: z.enum(['ripple', 'lift']).optional().describe('Whether to ripple delete (close gap) or lift (leave gap)')
    })
  • Dispatch in executeTool switch statement that routes calls to the removeFromTimeline handler after schema validation.
    case 'remove_from_timeline':
      return await this.removeFromTimeline(args.clipId, args.deleteMode);
  • Tool registration in getAvailableTools() array, providing name, description, and schema for MCP tool discovery.
    {
      name: 'remove_from_timeline',
      description: 'Removes a clip from the timeline.',
      inputSchema: z.object({
        clipId: z.string().describe('The ID of the clip on the timeline to remove'),
        deleteMode: z.enum(['ripple', 'lift']).optional().describe('Whether to ripple delete (close gap) or lift (leave gap)')
      })
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'removes' implies a destructive operation, the description doesn't specify whether this action is reversible, what permissions are required, or how it affects the timeline structure. The description mentions nothing about the consequences of removal or what happens to adjacent clips.

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 a single, efficient sentence that states the core functionality without unnecessary words. It's front-loaded with the essential action and resource, making it immediately understandable while being perfectly concise.

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 destructive operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after removal, whether the action can be undone, what permissions are needed, or how it interacts with other timeline elements. Given the complexity of video editing operations and the lack of structured safety information, more context is needed.

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 schema already fully documents both parameters (clipId and deleteMode with enum values). The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter documentation.

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 ('removes') and resource ('a clip from the timeline'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_sequence' or 'remove_effect', which would require more specific context about what distinguishes timeline clip removal from other deletion operations.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools that involve removal or deletion (delete_sequence, remove_effect), but the description doesn't explain when clip removal from a timeline is appropriate versus deleting an entire sequence or removing effects from clips.

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