premiere-pro-mcp

Overview Schema Source Related Servers Discussions Admin

Get Duplicate Media

get_duplicate_media

Read-onlyIdempotent

Find project items that reference the same source media file to consolidate duplicates. Filter by item-name substring and page through grouped results.

Instructions

Find project items that reference the same source media file. Useful for consolidation. After Effects compositions imported from the same .aep/.aepx are only grouped when their comp names also match. Groups are paged (default 100) and can be filtered by a case-insensitive item-name substring; follow nextOffset while truncated is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_duplicate_media"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum duplicate media groups (a group matches contains when any item name matches) entries to return (1-500, default 100).
`offset`	No	Zero-based index of the first duplicate media groups (a group matches contains when any item name matches) entry to return (default 0). Pass the previous response's nextOffset to read the next page.
`contains`	No	Optional case-insensitive substring matched against project item names before paging. Omit or pass an empty string to include every entry.
`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 read-only, non-destructive, idempotent, so the safety profile is covered. The description goes beyond them with genuine behavioral detail: After Effects comps only group when comp names match, groups page at a default of 100, filtering is case-insensitive, and callers must follow nextOffset while truncated is true — none of which is derivable from the 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?

Three tightly packed sentences, each carrying distinct information — purpose, the AE edge case, and the paging/filter protocol — with the core purpose front-loaded. Nothing is redundant padding.

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?

With an output schema present and thorough annotations, the description needn't explain return values, and it correctly covers the query semantics and paging contract. The remaining gap is that it never clarifies how its output relates to the consolidation tools that would consume it.

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 coverage is 100% and the schema already documents limit, offset, contains, and the CEP guard objects thoroughly. The description echoes the filter semantics and default page size but adds no syntax or format detail beyond the schema; baseline 3 applies where the schema does the heavy lifting.

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 — 'Find project items that reference the same source media file' — and adds a non-obvious scoping rule for imported .aep/.aepx comps. It doesn't name the sibling it is distinct from (consolidate_duplicates, find_items_by_media_path), so the agent must infer the boundary from intent alone.

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?

'Useful for consolidation' gestures at the follow-up action but never names consolidate_duplicates or says when to prefer this over find_items_by_media_path. Operational guidance for narrowing (contains filter) and paging is present, but the alternative-selection guidance 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