premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Preview Facility Metadata Intake

preview_facility_metadata_intake

Read-onlyIdempotent

Preview column-to-field mappings from an ALE table against reviewed source IDs before import. Detect duplicate keys, ambiguous filenames, missing sources and unsupported fields without writing Premiere metadata.

Instructions

Read a bounded ALE table and preview explicit column-to-named-field mappings against reviewed source IDs/filenames. Reports duplicate table keys, ambiguous filenames, missing sources and unsupported fields. Never writes Premiere metadata or requires an XMP packet dump.

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": {
      "path": "<path>",
      "match_column": "<match_column>",
      "column_mapping": "<column_mapping>",
      "sources": "<sources>"
    },
    "name": "preview_facility_metadata_intake"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Absolute caller-selected local file path. Referenced media is never opened automatically.
`sources`	Yes	Caller-reviewed bounded source catalog; duplicate filenames remain ambiguous.
`match_column`	Yes	ALE column matched exactly against caller-reviewed source filenames.
`column_mapping`	Yes	ALE column to supported facility field: Scene, Shot, Take, Tape, CameraRoll, SoundRoll, LogNote, Comment or Description. Other fields are reported unsupported.
`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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds genuine value by enumerating what the preview reports (duplicate table keys, ambiguous filenames, missing sources, unsupported fields) and by stating it needs no XMP packet dump. It does not describe result shape, but an output schema exists, so that omission is acceptable.

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 short sentences with zero waste: the operation and its inputs come first, then the reported diagnostics, then the non-mutation guarantee. Each sentence carries distinct information.

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?

The tool is a read-only preview with a rich seven-parameter schema and an output schema, and the description covers inputs, diagnostics and the no-write guarantee. It could go one step further by pointing to the follow-up action (e.g., the write/export counterpart) after a successful preview, but nothing essential for correct invocation is missing.

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 path, sources, match_column, column_mapping, idempotency_key and expected_cep_target is documented in structured data. The description reinforces the bounded-table and reviewed-source concepts but adds no syntax, format or constraint detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-plus-resource: read a bounded ALE table and preview column-to-named-field mappings against reviewed source IDs/filenames. 'Never writes Premiere metadata' implicitly separates it from mutating siblings such as set_metadata or set_xmp_metadata, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied: this is a validation/preview step before a facility metadata intake, useful when checking duplicate keys, ambiguous filenames, missing sources and unsupported fields. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g., export_facility_metadata_table) is offered for the case where the caller actually wants output.

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

Deploy Server