Skip to main content
Glama

trim_clip

Shorten a clip on the Premiere Pro timeline by adjusting its in and out points. Set a new duration or specify exact in/out points to refine edits.

Instructions

Adjusts the in and out points of a clip on the timeline, effectively shortening it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipIdYesThe ID of the clip on the timeline to trim
inPointNoThe new in point in seconds from the start of the clip
durationNoAlternative: set the desired timeline duration in seconds; cannot be combined with outPoint
outPointNoThe new out point in seconds from the start of the clip; cannot be combined with duration
Behavior2/5

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

With no annotations, the description carries full burden. It mentions adjusting points and shortening but does not disclose side effects, reversibility, or how it handles conflicting parameters (duration vs outPoint). Minimal behavioral context.

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?

Single sentence, clear and to the point with no unnecessary fluff. Well-structured for quick understanding.

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?

Tool is simple with 1 required param and schema covers all fields. However, the description does not mention the alternative duration parameter or any constraints (e.g., cannot combine duration with outPoint). Lacks sufficient context for full understanding without schema inspection.

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% so parameters are well documented. The description adds no additional meaning beyond what the schema provides, such as clarifying the relationship between duration and outPoint. Baseline of 3 is appropriate.

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?

Description clearly states it adjusts in/out points to shorten a clip, with a specific verb and resource. It distinguishes from trim-related siblings by focusing on the direct trim operation.

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?

The description implies usage for shortening a clip but offers no explicit guidance on when to use this vs alternatives like roll_edit or slip_edit. There are no exclusions or alternative recommendations.

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/compimprove/adobe-premiere-mcp'

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