Skip to main content
Glama

slide_edit

Perform a slide edit on Premiere Pro timelines, moving the edit point between adjacent clips without altering clip durations.

Instructions

Premiere Pro expanded operation: slide edit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a timeline-editing operation, but it does not explain what slide edit changes, whether selections are required, what side effects occur on neighboring clips, or what the tool returns.

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 short, but this is under-specification rather than genuine conciseness. The only substantive term, 'slide edit', repeats the tool name and provides little usable information.

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?

This tool has no annotations, no output schema, and no parameter structure to compensate, yet the description explains almost nothing about behavior, requirements, or expected result. Among dozens of editing siblings, it leaves an agent unable to determine how to invoke it correctly.

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?

The input schema has zero parameters, so there is no parameter semantics to document. The empty schema and 100% coverage mean the description does not need to add parameter-level detail.

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

Purpose2/5

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

The description essentially restates the tool name: 'slide edit' adds no verb or outcome, and 'expanded operation' is a generic qualifier. It does not distinguish this from sibling editing tools such as roll_edit, slip_edit, or trim_clip.

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?

There is no guidance about when to use slide_edit versus the many related editing tools. The phrase 'expanded operation' vaguely implies an advanced trim, but it provides no concrete context, prerequisites, or alternatives.

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