Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_from_timeline

Remove a clip from the Premiere Pro timeline using its ID, with options to ripple delete to close gaps or lift to leave gaps. Specify a sequence when targeting non-active sequences.

Instructions

Removes a clip from the timeline. Pass sequenceId when the clip ID came from list_sequence_tracks for a non-active sequence.

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": {
      "clipId": "<clipId>"
    },
    "name": "remove_from_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYesThe ID of the clip on the timeline to remove
deleteModeNoWhether to ripple delete (close gap) or lift (leave gap)
sequenceIdNoOptional sequence ID to search. If omitted, searches the active sequence first, then all sequences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses one behavioral nuance (sequenceId needed for non-active sequences) but does not mention whether removal is destructive/undoable, how deleteMode affects the timeline, or what happens to the source clip.

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 with the main purpose front-loaded and a single high-value conditional detail. No filler or repetition of schema data.

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

Completeness3/5

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

The description plus schema adequately covers the core operation and key sequenceId case, but with no output schema and no annotations, it leaves gaps around expected return behavior and differentiation from sibling removal tools. Minor gaps prevent a higher score.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by tracing clipId origin to list_sequence_tracks and clarifying when sequenceId is required, which goes beyond the schema's generic parameter descriptions.

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?

The description clearly states the action ('Removes a clip from the timeline') with a specific resource and scope. It distinguishes itself from sibling tools like remove_selected_clips or ripple_delete by targeting a clip by ID.

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

Usage Guidelines3/5

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

Provides a specific usage condition for sequenceId ('Pass sequenceId when the clip ID came from list_sequence_tracks for a non-active sequence'), but does not explicitly discuss when to use this tool versus alternative removal tools or when not to use it.

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