Premiere Pro MCP Server

Plan Short Subscribe Cta

plan_short_subscribe_cta

Read-onlyIdempotent

Plan a subscribe CTA overlay for Shorts, placed after the hook in a platform-safe lower-third. Generates a local-only timing and copy plan without altering Premiere.

Instructions

Plan a brief subscribe overlay about two-thirds through a Short, after an optional hook, in a platform-safe lower-third. Local-only; never changes Premiere.

Input Schema

TableJSON Schema

Name	Required	Description
`copy`	No	Optional overlay text. Defaults to a brand-appropriate subscribe line.
`brand`	No	Channel brand kit. cafe must not reuse watch_club fonts, name cards, or speaker colors.
`at_ratio`	No	Placement as a fraction of duration; defaults to 2/3.
`platform`	No	Safe-zone profile; defaults to youtube_shorts.
`frame_rate`	No	Sequence frame rate used to snap times to frames; defaults to 30.
`hold_seconds`	No	How long the prompt stays on screen; defaults to 2.
`duration_seconds`	Yes	Finished Short duration in seconds.
`hook_end_seconds`	No	If the hook ends later than the default placement, the CTA starts after the hook.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.0Sep 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context with 'Local-only; never changes Premiere,' clarifying that the tool produces a plan without modifying the project. No contradiction with annotations.

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 short sentences with no filler. The core placement logic is front-loaded, and the behavioral guarantee is a compact second sentence. Every word earns its place.

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?

Given the rich schema, output schema, and annotations, the description covers the essential purpose and safety profile. It lacks explicit alternative routing, but that is a usage-guidance gap rather than a completeness gap for invoking the tool correctly.

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 all 8 parameters are already documented in the input schema. The description adds no parameter-level detail beyond schema, 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 'Plan' with resource 'brief subscribe overlay' and specifies placement ('about two-thirds through a Short', 'after an optional hook', 'platform-safe lower-third'). This clearly distinguishes it from sibling plan_* tools by targeting subscribe CTA overlays specifically.

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 its use case—planning a subscribe overlay for a Short—but provides no explicit when-to-use guidance, exclusions, or references to alternative tools. An agent must infer when to select this over other plan_* siblings.

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

Deploy Server