Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

roll_edit

Adjust an edit point between two adjacent clips by rolling the clip boundary left or right using a given offset in seconds.

Instructions

Perform a roll edit on a clip (adjusts the edit point between two adjacent clips). Uses QE DOM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip
offset_secondsYesOffset in seconds (positive = roll right, negative = roll left)
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It vaguely states 'adjusts the edit point' but doesn't mention timeline modification, potential sync issues, or prerequisites like adjacent clips. Lacks detail for safe invocation.

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 sentences, front-loaded with the action, no wasted words. Efficient and clear.

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?

Given simple parameters and no output schema, the description is adequate but lacks details on edge cases (e.g., offset limits) or undo behavior. Completeness is sufficient but not thorough.

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% with descriptions for node_id and offset_seconds. The description adds no additional meaning beyond the schema, meeting baseline but not enhancing understanding.

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 tool performs a 'roll edit on a clip' and explains it adjusts the edit point between two adjacent clips, distinguishing it from siblings like slide_edit or slip_edit.

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?

No explicit guidance on when to use roll_edit versus alternatives like trim_clip, slide_edit, or slip_edit. The description implies usage for adjusting edit points but lacks when-not-to-use scenarios.

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