premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Plan Platform Delivery Matrix

plan_platform_delivery_matrix

Read-onlyIdempotent

Plan multi-ratio delivery of one source sequence to TikTok, Reels, Shorts, YouTube, LinkedIn, X, and Facebook, with reframe scale math, duration and file-size fit, caption safe zones, and ordered apply routes.

Instructions

Plan multi-ratio delivery of one source sequence to TikTok, Reels, Shorts, YouTube, LinkedIn, X, and Facebook from a local spec table: sequence settings, reframe scale math, duration and file-size fit, caption safe zones, and ordered apply routes. Local-only; never 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": {
      "source": "<source>",
      "targets": "<targets>"
    },
    "name": "plan_platform_delivery_matrix"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	Source sequence characteristics.
`targets`	Yes	Unique platform ids to plan for.
`strategy`	No	Reframe strategy when the aspect ratio changes; defaults to auto_reframe.
`export_preset_hint`	No	Optional export preset name to echo into the export step.
`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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description reinforces this with 'Local-only; never changes Premiere' plus the fact that output is a plan with 'ordered apply routes' — useful context about what the agent receives. It stops short of stating that no host state is inspected or that repeated calls are deterministic, but the key safety profile is clear.

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?

Two dense sentences, front-loaded with the action and platform targets, then the local-only constraint. The mid-sentence list of computed outputs is long but each item maps to a distinct planning concern, so little is wasted.

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 a full output schema covering return values, rich annotations, and complete parameter documentation, the description supplies what's missing: scope, platform set, and the non-mutating guarantee. For a 6-parameter tool with deep nested guard objects, one could ask for a sentence on when expected_cep_target matters, but that is adequately handled 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%, so every parameter including the nested CEP guard objects is documented in the schema itself. The description adds only that a single source sequence is planned against multiple platforms and that aspect-ratio/reframe math is involved, without elaborating on strategy options or the guard parameters beyond what the schema says. 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?

States a specific verb ('Plan') and a precisely scoped resource: a multi-ratio delivery matrix for one source sequence across named platforms. It enumerates the plan's contents (sequence settings, reframe scale math, duration/file-size fit, caption safe zones, apply routes), which separates it from siblings like validate_platform_publish_package or plan_short_export_folder without the agent needing to open a schema.

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?

'Local-only; never changes Premiere' implies this is the planning step taken before any real export or mutation, but no explicit alternative is named (e.g., which sibling validates the resulting package or performs the export). Usage is implied rather than directed.

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

Deploy Server