Skip to main content
Glama

roll_edit

Perform a roll edit on a Premiere Pro timeline to move the cut point between two adjacent clips, preserving the total sequence duration.

Instructions

Premiere Pro expanded operation: roll edit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

D1.3/5.0
Behavior1/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does not mention side effects, requirements, or how the tool interacts with the timeline or selected clips. It says only 'roll edit' with no explanation of the operation's behavior.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than efficient conciseness. It provides no substantive information, so the brevity is not a strength—it fails to communicate essential details.

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

Completeness1/5

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

For an editing operation with no output schema, no annotations, and no parameter explanation, the description is entirely inadequate. An agent has no idea what a roll edit does, when to invoke it, or what the outcome will be. The context is completely missing.

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

Parameters2/5

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

The input schema is an empty object with additionalProperties true, and there are no defined parameters. The description adds no information about how the tool determines its target (e.g., selected clips, playhead position) or whether any implicit inputs are used. It does not compensate for the lack of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Premiere Pro expanded operation: roll edit' restates the tool name without explaining what a roll edit is or what it does. It does not distinguish this tool from other editing operations like trim_clip or move_clip, providing no idea of its function in Premiere Pro.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No context, prerequisites, or conditions for use are given. The description mentions 'expanded operation' but fails to clarify what that means or when it applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/tro2789/scout-premiere-mcp'

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