Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Duplicate Media

get_duplicate_media
Read-onlyIdempotent

Identify project items referencing the same source media file to streamline consolidation. Filter by item name substring, then page through results to find all duplicates.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum duplicate media groups (a group matches contains when any item name matches) entries to return (1-500, default 100).
offsetNoZero-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.
containsNoOptional case-insensitive substring matched against project item names before paging. Omit or pass an empty string to include every entry.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties
      Added value: +{
+  "contains": {
+    "description": "Optional case-insensitive substring matched against project item names before paging. Omit or pass an empty string to include every entry.",
+    "maxLength": 256,
+    "type": "string"
+  },
+  "limit": {
+    "description": "Maximum duplicate media groups (a group matches contains when any item name matches) entries to return (1-500, default 100).",
+    "maximum": 500,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "offset": {
+    "description": "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.",
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • 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."
  2. Changed1 schema field changedv1.14.9
    • removedInput schema / properties
      Removed value: -{}
  3. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  4. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: After Effects comps are grouped only when comp names also match, and the result set is paged with a truncation signal. That is real context beyond structured data.

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 'what' before the AE-specific caveat and paging mechanics. Four sentences, each carrying information, though the paging sentence partly overlaps with schema text.

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 annotations covering safety and an output schema covering the return shape, the description supplies the missing nuance an agent needs: the AE comp-name grouping rule and the truncation/nextOffset loop. Remaining gaps are minor for a read-only list tool.

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 each parameter is already documented, including the default of 100 and the nextOffset round-trip. The description largely restates this, adding only the case-insensitivity and substring framing that the schema also carries, so the baseline 3 applies.

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 first sentence states a precise verb+resource+scope ('project items that reference the same source media file'), which distinguishes it from near-neighbors like find_items_by_media_path (path lookup) and consolidate_duplicates (the mutating action). An agent can identify the operation 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 Guidelines4/5

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

It orients usage ('Useful for consolidation') and gives concrete operational instructions for filtering and paging ('follow nextOffset while truncated is true'). It stops short of explicit when-not guidance or naming the sibling that performs the actual consolidation.

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

Deploy Server

Other Tools