Premiere Pro MCP Server

Create Editorial Context Pack

create_editorial_context_pack

Read-onlyIdempotent

Build a compact Markdown reading view from captured local transcript, shot, audio, note, source, or timeline context for editorial review, returning stable evidence IDs and revisions.

Instructions

Create a compact Markdown reading view from already captured local transcript, shot, audio, note, source, or timeline context. It returns stable evidence IDs and context revisions for review, never calls an AI/provider or Premiere, and cannot change the project.

Input Schema

TableJSON Schema

Name	Required	Description
`kinds`	No	Optional context-kind filter. Omit to retrieve all matching local evidence.
`intent`	Yes	The editorial question used to retrieve and compact local evidence.
`project_id`	Yes	Project context ID returned by manage_project_context capture.
`max_entries`	No	Maximum matching evidence entries to include.
`sequence_id`	No	Optional exact sequence ID filter.
`max_characters`	No	Strict maximum length of the Markdown reading view.

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/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, so the safety profile is largely covered. The description still adds genuinely new context: it never calls an AI/provider or Premiere, and it returns stable evidence IDs and context revisions for downstream review — information annotations cannot convey.

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, front-loaded with the primary action and scope, followed by the crucial non-invocation guarantee. No filler.

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?

For a read-only, idempotent tool with full schema coverage and an output schema, the description supplies the missing pieces: the source prerequisite and the no-external-call guarantee. Minor omission is any pointer to alternatives, but nothing critical for correct invocation is absent.

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 parameter documentation is already complete; the description only echoes the kind list. Baseline 3 is appropriate since the description adds little beyond the schema for the six 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 and artifact ('Create a compact Markdown reading view') plus the exact source material (transcript, shot, audio, note, source, timeline context). An agent can distinguish this from search_project_context or create_context_edit_plan without opening the 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?

The phrase 'from already captured local context' implies the prerequisite that context must first be captured (via manage_project_context), which is useful. However, it never states when to prefer this over siblings like search_project_context or preview_editorial_plan, so usage is only implied.

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

Deploy Server