premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Create Editorial Context Pack

create_editorial_context_pack

Read-onlyIdempotent

Creates a compact Markdown reading view from captured transcript, shot, audio, note, source, or timeline evidence for editorial review, returning stable evidence IDs and context 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.

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": {
      "project_id": "<project_id>",
      "intent": "<intent>"
    },
    "name": "create_editorial_context_pack"
  }
}

Input 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.
`idempotency_key`	No	Optional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
`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.7/5.0

Behavior5/5

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

The description provides critical behavioral guarantees beyond the hints provided in the annotations. For example, the guarantee that it 'cannot change the project' is a vital safety constraint, and the disclosure that it 'never calls an AI/provider' is key architectural context.

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?

The definition is highly efficient, using only two sentences. The first sentence defines the action and resource, while the second front-loads the critical behavioral constraints, optimizing its structure for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (9 parameters, CEP requirements), the definition is fully complete. It defines the scope of the context, the nature of the output, and critical functional boundaries, leaving the agent fully informed without requiring external documentation.

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?

Since the schema coverage is 100%, the schema handles the technical definition of parameters (like 'kinds'). The description adds semantic context by confirming the evidence is 'already captured local' evidence, which is already largely implied by the input structure.

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?

The description clearly states the action and the output resource: 'Create a compact Markdown reading view'. It specifies the input material (transcript, shot, audio, etc.), making the purpose highly actionable and distinct from project modification tools.

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

Usage Guidelines5/5

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

It provides explicit constraints defining when and how the tool should be used: it is intended for 'review' of evidence and specifically states what it will NOT do ('never calls an AI/provider or Premiere'). This prevents inappropriate use cases.

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

Deploy Server