Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Crop Clip

crop_clip

Apply or update Adobe Premiere Pro's Crop effect on one video clip, set crop edges, feather, and zoom, then read back requested values.

Instructions

Apply or update Premiere's Crop effect on one video clip and read back every requested value. Adding Crop uses the legacy QE catalog only when the clip does not already contain it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoPercent cropped from the top edge.
leftNoPercent cropped from the left edge.
zoomNoWhether Crop should scale the remaining image to fill the frame.
rightNoPercent cropped from the right edge.
bottomNoPercent cropped from the bottom edge.
node_idYesTimeline video-clip node ID.
edge_featherNoCrop edge feather percentage.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.6
    • changedOutput schema / properties / data / description
      Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."
  2. Changed13 schema fields changedv1.14.9
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bottom / maximum
      Added value: +100
    • addedInput schema / properties / bottom / minimum
      Added value: +0
    • addedInput schema / properties / edge_feather / maximum
      Added value: +100
    • addedInput schema / properties / edge_feather / minimum
      Added value: +0
    • addedInput schema / properties / left / maximum
      Added value: +100
    • addedInput schema / properties / left / minimum
      Added value: +0
    • addedInput schema / properties / node_id / maxLength
      Added value: +512
    • addedInput schema / properties / node_id / minLength
      Added value: +1
    • addedInput schema / properties / right / maximum
      Added value: +100
    • addedInput schema / properties / right / minimum
      Added value: +0
    • addedInput schema / properties / top / maximum
      Added value: +100
    • addedInput schema / properties / top / minimum
      Added value: +0
  3. Addedv1.14.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-destructive and non-idempotent behavior. The description adds useful context beyond annotations by noting that adding Crop uses the legacy QE catalog only when the clip does not already contain the effect, and that it reads back every requested value. It does not cover permissions or rate limits, but the extra implementation detail is valuable.

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?

The description is two tightly written sentences with no filler. The core purpose is front-loaded, and the second sentence adds a specific behavioral nuance without bloating the definition.

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

Completeness4/5

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

With a full output schema and annotations covering safety, the description provides enough to call the tool correctly. It explains the main action and a key conditional for adding the effect, though it could add more about prerequisites or how it differs from generic effect tools.

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 description coverage is 100%, so all seven parameters are already documented. The description adds no parameter-level syntax or format details beyond the schema, making the baseline 3 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?

The description states a specific verb (apply or update) and resource (Premiere's Crop effect) on a clearly scoped object (one video clip). It is distinguishable from generic effect siblings like apply_effect or set_clip_properties because it names the exact effect and the read-back behavior.

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 when to use it by naming the Crop effect and one video clip, but it does not explicitly state when to prefer this over siblings such as apply_effect, batch_apply_effect, or set_clip_properties. No when-not conditions or alternatives are provided.

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

Deploy Server

Other Tools