Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

remove_from_timeline

Delete a clip from the timeline using its node ID, with the option to perform a ripple delete to remove the gap.

Instructions

Remove a clip from the timeline

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip to remove
rippleNoWhether to ripple delete (close the gap). Default: false
Behavior2/5

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

The description minimally states the action but does not disclose behavioral aspects beyond that. For example, it does not mention that the 'ripple' parameter controls gap closure, nor does it clarify whether this removes the clip from the timeline entirely or just its track position. With no annotations, the description carries the full burden and falls short.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the primary action. While efficient, it omits useful details like the ripple behavior, which could be added without sacrificing brevity.

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?

Given the lack of annotations and output schema, the description is insufficient. It does not explain prerequisites, consequences, or the exact effect (e.g., whether it deletes the clip from the project or just the timeline). The presence of sibling tools with similar names underscores the need for more context.

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%, meaning both parameters are described in the schema. The description adds no additional meaning beyond 'remove a clip', so it meets the baseline expectation but does not improve understanding of the parameters.

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 'Remove a clip from the timeline', specifying the action and resource. However, it does not distinguish this tool from sibling tools like 'remove_selected_clips' or 'ripple_delete', which may have similar purposes.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as the clip needing to exist on the timeline, or conditions like whether the clip must be selected.

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/leancoderkavy/premiere-pro-mcp'

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