premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Metadata

get_metadata

Read-onlyIdempotent

Retrieve bounded metadata for a Premiere Pro project item, with parsed fields by default and optional opt-in access to sensitive GPS, serial, contact, media path, or raw project/XMP packets.

Instructions

Get metadata for a project item. Returns bounded parsed fields by default; GPS, serials, and personal contact/author fields are omitted. Raw packets require explicit include_project_metadata/include_xmp_metadata and include_sensitive true. Media paths require include_media_path true. Project metadata XML and file/clip XMP are separate packets; disable either when identity/path is enough. Prefer inspect_project_panel_metadata_uxp item_columns or manage_metadata_uxp inspect_fields for visible columns. This is not the premiere://project/metadata resource. GPS and serials are omitted from parse_fields unless include_sensitive is true.

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": {
      "item_id": "<item_id>"
    },
    "name": "get_metadata"
  }
}

Input Schema

Name	Required	Description
`item_id`	Yes	Node ID or name of the project item, or the sequence ID of a sequence
`parse_fields`	No	Parse project metadata and XMP into named fields (default true). Set false for identity-only or explicitly requested raw packets.
`include_sensitive`	No	Opt in to sensitive GPS, serial, author, and contact fields. Required for any raw packet; default false.
`include_media_path`	No	Opt in to the full source media path, which can identify the local user and folders; default false.
`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.
`include_xmp_metadata`	No	Opt in to raw XMP XML (maximum 256 Ki characters). Requires include_sensitive true; default false. Set false to skip reading this packet entirely.
`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.
`include_project_metadata`	No	Opt in to raw Project Metadata XML (maximum 256 Ki characters). Requires include_sensitive true; default false. Set false to skip reading this packet entirely.

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: GPS, serials and author/contact data are suppressed unless include_sensitive is true, and raw packets cost extra reads. It does not discuss output size, error conditions on unsaved projects, or truncation behavior, keeping it below a 5.

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?

Front-loaded with the core action and default behavior, then opt-in conditions, then alternatives and disambiguation — a sensible ordering. The closing sentence ("GPS and serials are omitted from parse_fields unless include_sensitive is true") repeats the third sentence almost verbatim, which is wasted space in an otherwise dense paragraph.

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?

An output schema exists, so return-value shape need not be described; the description instead covers the privacy gating, packet selection, and alternative tools that the schema cannot express. For an 8-parameter read tool with nested identity guards, an agent has enough to both select and invoke it 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 the baseline is 3. The description restates the include_sensitive gating for raw packets and media paths, but that dependency is already stated in the individual schema property descriptions ("Requires include_sensitive true"), so it adds little beyond the schema rather than new cross-parameter meaning.

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 and resource ("Get metadata for a project item") and scopes the default return to bounded parsed fields. It disambiguates from the URI resource ("This is not the premiere://project/metadata resource") and from XMP packets, but never names the closest siblings in this server — get_xmp_metadata, get_project_panel_metadata, get_project_item_info — so the agent must still infer which one to pick.

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

Usage Guidelines4/5

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

Gives explicit defaults (parsed fields on, sensitive/paths off), the opt-in condition for each packet type, and a rule to disable packets when identity/path suffices. It also routes the agent elsewhere ("Prefer inspect_project_panel_metadata_uxp item_columns or manage_metadata_uxp inspect_fields for visible columns"), though those targets are not siblings in this server, so the routing is only partly actionable.

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

Deploy Server