Premiere Pro MCP Server

Get Unused Media

get_unused_media

Read-onlyIdempotent

Identify project media not referenced by any sequence, helping clean up Premiere Pro projects. Filter results by name and page through large lists.

Instructions

Find project items that are NOT used in any sequence. Useful for cleaning up projects. Results are paged (default 100 items) and can be filtered by a case-insensitive name substring; follow nextOffset while truncated is true.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum unused project items entries to return (1-500, default 100).
`offset`	No	Zero-based index of the first unused project items 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.

Output Schema

TableJSON 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.18.6Sep 30, 2026

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 unused project items entries to return (1-500, default 100).",
+    "maximum": 500,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "offset": {
+    "description": "Zero-based index of the first unused project items 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."

Changed1 schema field changedv1.14.9Sep 8, 2026
- removedInput schema / properties
```
Removed value: -{}
```

Changed2 schema fields changedv1.14.4Aug 29, 2026

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"
+}

First observedv1.1.1May 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds valuable behavioral context about paging defaults, case-insensitive filtering, and following nextOffset while truncated is true.

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?

Two sentences with zero waste; the core purpose is front-loaded, followed by practical paging and filtering details. Every clause earns its place.

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?

With an output schema present, the description need not explain return values. It covers the core purpose, the cleanup use case, and the paging/filtering mechanics that an agent needs to invoke the tool 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 schema documents limit, offset, and contains fully. The description repeats the default page size and filter behavior but adds little parameter syntax beyond what is already in the schema, so the baseline 3 is appropriate.

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?

States a specific verb ('Find') and resource ('project items that are NOT used in any sequence'), and distinguishes itself from the sibling get_used_media_report by stating the inverse scope. An agent can immediately tell what the tool returns without reading 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?

Gives a clear use case ('Useful for cleaning up projects') and describes paging/filtering behavior. It does not explicitly name when to prefer it over alternatives like list_project_items or get_used_media_report, so it falls short of full when/when-not guidance.

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

Deploy Server