premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Validate Platform Publish Package

validate_platform_publish_package

Read-onlyIdempotent

Validates rendered video files and post metadata against a platform's 2026 publish limits, flagging hard violations and soft warnings with normalized hashtags and character counts.

Instructions

Validate a rendered file plus title, description, hashtags, and content flags against one platform's approximate 2026 publish limits. Returns hard violations, soft warnings, normalized hashtags, and character counts. Local-only; never uploads 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>",
      "duration_seconds": "<duration_seconds>",
      "width": "<width>",
      "height": "<height>",
      "frame_rate": "<frame_rate>"
    },
    "name": "validate_platform_publish_package"
  }
}

Input Schema

Name	Required	Description
`title`	No	Post or video title.
`width`	Yes	Rendered frame width in pixels.
`height`	Yes	Rendered frame height in pixels.
`hashtags`	No	Hashtags to publish with the post.
`platform`	Yes	Target platform id.
`container`	No	Container extension such as mp4 or mov.
`frame_rate`	Yes	Rendered frame rate in frames per second.
`audio_codec`	No	Audio codec name such as AAC.
`description`	No	Post caption or description body.
`video_codec`	No	Video codec name such as H.264.
`has_captions`	No	Whether captions are burned in or attached.
`content_flags`	No	Disclosure flags that trigger platform label reminders.
`file_size_bytes`	No	Rendered file size in bytes.
`duration_seconds`	Yes	Rendered file duration in seconds.
`expected_cep_target`	No	Optional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
`expected_project_path`	No	Optional 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

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.
`receipt`	No	Versioned common mutation receipt; success never implies rendered verification.
`idempotency`	No	Present 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.

First observedv1.30.0Nov 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, and the description reinforces rather than contradicts them with 'Local-only; never uploads or changes Premiere.' It also adds a real behavioral caveat — the limits are 'approximate 2026' platform limits — which tells the agent results are advisory, but it omits whether violations block or merely advise downstream.

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?

Three tight sentences: what is validated, what comes back, and what it will never do. The most decision-relevant clause (platform limits) is front-loaded and nothing is padded.

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 16 params including a nested CEP guard object and an output schema present, the description covers purpose, output shape summary, and side-effect safety adequately. The only gap is that the expected_cep_target/expected_project_path guards sit oddly against a 'never changes Premiere' tool, and the description does not explain whether they are relevant here.

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 coverage is 100%, so every field is already documented in-schema; the baseline of 3 applies. The description enumerates a few of the 16 inputs (title, description, hashtags, content flags) but adds no format, unit, or interaction detail beyond the schema — notably it says nothing about the platform enum or the CEP guard parameters.

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 (validate) and resource (a rendered file plus publish metadata: title, description, hashtags, content flags) against a named scope (one platform's approximate 2026 publish limits). That scope cleanly separates it from generic siblings like validate_export_preset or verify_delivery_conformance without needing to name them.

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 the pre-publish use case but never states when to pick this over neighbors such as plan_platform_delivery_matrix or validate_export_preset, nor any exclusions. Usage is inferable rather than spelled out.

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

Deploy Server