Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

set_sequence_pixel_aspect_ratio

Adjust the pixel aspect ratio of the active sequence to match different video formats, such as square pixels or DV widescreen.

Instructions

Change the pixel aspect ratio of the active sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratioYesPixel aspect ratio (1.0 for square pixels, 1.4222 for 16:9 DV, etc.)
Behavior2/5

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

The description only says 'change', implying mutation, but with no annotations, it lacks disclosure of side effects (e.g., impact on existing clips, reversibility, permission requirements). For a mutation tool, this is insufficient 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.

Conciseness4/5

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

The description is a single sentence with no unnecessary words. It is front-loaded and efficient, but could benefit from slightly more context without losing conciseness.

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 simplicity (one param, no output schema), the description is minimal. It does not explain consequences for the timeline, whether it affects existing clips, or how it relates to sibling tools. More context would improve completeness.

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?

The input schema already describes the ratio parameter with examples. The description adds no additional meaning beyond what the schema provides. With 100% schema coverage, baseline is 3.

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

Purpose4/5

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

The description clearly states it changes the pixel aspect ratio of the active sequence, using a specific verb and resource. It implicitly distinguishes from sibling tool 'set_override_pixel_aspect_ratio' (which applies to clips) but does not differentiate from 'set_sequence_settings' which might also alter PAR.

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 set_sequence_settings or set_override_pixel_aspect_ratio. No prerequisites or exclusions provided.

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