Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

set_override_pixel_aspect_ratio

Override the pixel aspect ratio of a project item by specifying numerator and denominator values to correct or adjust pixel shape.

Instructions

Override the pixel aspect ratio of a project item

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item
numeratorYesPAR numerator (e.g., 1 for square pixels)
denominatorYesPAR denominator (e.g., 1 for square pixels)
Behavior2/5

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

No annotations exist. Description only states 'Override' without disclosing side effects (e.g., reversibility, required permissions, impact on linked media). Minimal behavioral disclosure.

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?

Single sentence, directly states purpose. No wasted words, though could benefit from additional context without adding length.

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?

No output schema; description does not explain what happens after override (e.g., return value, autosave behavior). Lacks completeness for a tool with zero annotations.

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 covers 100% of parameters with descriptions for each (e.g., 'PAR numerator (e.g., 1 for square pixels)'). The tool description adds no extra parameter meaning, so baseline 3 applies.

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 uses specific verb 'Override' and resource 'pixel aspect ratio of a project item', clearly differentiating from siblings like 'set_sequence_pixel_aspect_ratio' and 'set_override_frame_rate'. No ambiguity.

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 provided on when to use this tool versus alternatives, such as 'set_sequence_pixel_aspect_ratio'. No mentions of prerequisites, exclusions, or context.

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