Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

trim_clip

Trim a clip's in or out point by specifying new timestamps relative to the source media.

Instructions

Trim a clip's in or out point

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode ID of the clip to trim
new_in_secondsNoNew in-point in seconds (relative to clip's source media)
new_out_secondsNoNew out-point in seconds (relative to clip's source media)
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states the action. It does not mention if trimming is destructive, whether it affects linked clips, or if changes are reversible. This is insufficient for an agent to understand side effects.

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 sentence with no waste. However, given the simplicity, it could be slightly more informative without losing conciseness. Still, it is efficient and front-loaded.

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 existence of many sibling trimming tools, the description is too brief. It lacks details like relative to source media, that only one of new_in_seconds or new_out_seconds is needed to achieve a single-point trim, and what happens to the other point. Without output schema, agent has no info on return values.

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% (all parameters described in schema), so baseline is 3. The description 'Trim a clip's in or out point' adds no additional meaning beyond schema parameter names and descriptions, missing context like relative to source or optionality of in/out.

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 trims a clip's in or out point, using specific verb 'Trim' and resource 'clip's in or out point'. It differentiates from sibling tools like split_clip (splits) or slip_edit (adjusts both points equally).

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 on when to use this tool versus alternatives like slip_edit, slide_edit, or split_clip. The description does not mention prerequisites, context, or scenarios where this tool is preferred.

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