Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by matt-j-penny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check Caption Safe Zone

check_caption_safe_zone
Read-onlyIdempotent

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

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>",
      "frame": "<frame>",
      "elements": "<elements>"
    },
    "name": "check_caption_safe_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameYesOutput frame size in pixels; used for orientation checks and pixel readback.
elementsYesOn-screen rectangles normalized to the frame (0..1), with x,y at the top-left corner.
platformYesTarget platform whose UI overlays are checked.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output 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.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds meaningful context beyond that: zones are 'approximate' (an accuracy caveat), the tool only suggests rather than applies a position, and it explicitly never touches Premiere — a real behavioral claim, not a restatement of hints.

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 sentences, front-loaded with the action and scope, followed by the execution model and side-effect disclaimer. Every clause carries information an agent needs; nothing is padding.

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 an output schema present and full annotations, the description needn't explain return values, and it does supply the key caveats (approximate zones, local-only, no Premiere access). Minor gap: it doesn't hint at tolerance/severity semantics or element-count limits, though those live in the schema.

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% and the nested frame/elements/platform structure is fully documented in-schema, so baseline 3 applies. The description reinforces that rects are caller-supplied and normalized, and lists the platform set that mirrors the enum, but adds no format or constraint detail beyond the schema.

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 verb (check), specific resources (caption, title, logo, graphic rectangles), the comparison target (approximate platform UI overlay zones) and a secondary action (suggest the nearest clear position). The enumerated platform list makes the scope unambiguous and no sibling tool performs this geometry check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'Local-only geometry on caller-supplied normalized rects; it never reads or changes Premiere' clearly delimits when this applies: pre-placement planning with rects already in hand, not timeline inspection. No explicit alternative is named (e.g. plan_platform_delivery_matrix or get_caption_style_guidance), so routing to siblings is left to inference.

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