Premiere Pro MCP Server

Check Caption Safe Zone

check_caption_safe_zone

Read-onlyIdempotent

Check caption, title, logo, and graphic rectangles against TikTok, Reels, Shorts, feed, YouTube, LinkedIn, or X UI overlay zones and suggest the nearest clear position.

Instructions

Check caption, title, logo, and graphic rectangles against approximate platform UI overlay zones (TikTok, Reels, Shorts, feed, YouTube, LinkedIn, X) and suggest the nearest clear position. Local-only geometry on caller-supplied normalized rects; it never reads or changes Premiere.

Input Schema

TableJSON Schema

Name	Required	Description
`frame`	Yes	Output frame size in pixels; used for orientation checks and pixel readback.
`elements`	Yes	On-screen rectangles normalized to the frame (0..1), with x,y at the top-left corner.
`platform`	Yes	Target platform whose UI overlays are checked.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.18.6Sep 30, 2026

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."

Addedv1.14.9Sep 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world safety. The description adds valuable context: it operates local-only on caller-supplied normalized rects, uses approximate overlay zones, and never reads or changes Premiere. This goes beyond the annotations but stops short of describing output format or edge cases.

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?

Two tight sentences: the first states the core action and result, the second clarifies local-only scope and Premiere isolation. It is front-loaded and every sentence earns its place.

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

Completeness5/5

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

Given the existing output schema and rich annotations, the description provides everything needed: purpose, scope, platform list, local-only behavior, and explicit non-interaction with Premiere. No significant gaps remain for correct invocation.

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 the schema fully documents all three parameters. The description mentions 'caller-supplied normalized rects' and lists platform names, but adds little semantic detail beyond what the schema already provides.

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?

States a specific action: check caption, title, logo, and graphic rectangles against platform UI overlay zones and suggest the nearest clear position. It names the resource (rectangles, overlay zones) and lists target platforms, making it immediately distinguishable from sibling tools.

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?

Usage is implied for checking safe zones, but the description does not explicitly say when to use this tool versus alternatives like validate_platform_publish_package or get_caption_style_guidance. No exclusions or prerequisites are stated.

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

Deploy Server