Premiere Pro MCP Server

Get Bin Contents

get_bin_contents

Read-onlyIdempotent

Fetch detailed contents of a Premiere Pro bin using its name, node ID, or path. Returns nested items, media paths, offline status, color labels, and metadata, with optional recursive depth and pagination.

Instructions

Get detailed contents of a specific bin (folder) including all nested items, media paths, offline status, color labels, and metadata. Searches by bin name or node ID.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum direct children to return. Pair with recursive false for the smallest bounded response.
`bin_id`	Yes	Bin name, node ID, or path (e.g., 'Footage', 'Footage/Raw')
`offset`	No	Zero-based offset into the bin's direct children. Pair with limit for a bounded page.
`max_depth`	No	Maximum nested-bin depth when recursive is true. Defaults to the legacy unlimited recursion.
`recursive`	No	Include items from sub-bins recursively (default: true)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the tool completed successfully.
`data`	No	Tool-specific result data when ok is true.
`tool`	Yes	The registered MCP tool name.
`error`	No	Failure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.14.9Sep 8, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +500
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / type
```
Added value: +"integer"
```
- addedInput schema / properties / max_depth / maximum
```
Added value: +10
```
- addedInput schema / properties / max_depth / minimum
```
Added value: +0
```
- addedInput schema / properties / max_depth / type
```
Added value: +"integer"
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- addedInput schema / properties / offset / type
```
Added value: +"integer"
```

Changed5 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"

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum direct children to return. Pair with recursive false for the smallest bounded response."
+}

addedInput schema / properties / max_depth

Added value: +{
+  "description": "Maximum nested-bin depth when recursive is true. Defaults to the legacy unlimited recursion."
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Zero-based offset into the bin's direct children. Pair with limit for a bounded page."
+}

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

Changed1 schema field changedv1.4.0Jul 27, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.1.1May 28, 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, and non-destructive behavior. The description adds useful behavioral context by listing what the response includes: media paths, offline status, color labels, and metadata. It also discloses that lookup can be by name or node ID. It does not contradict annotations, though 'all nested items' is slightly oversimplified given the recursive parameter.

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 focused sentences with no filler. The first sentence front-loads the tool's purpose and key return contents, and the second adds identifier flexibility. Every part earns its place.

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 output schema and annotations cover the return structure and safety profile, while the parameter schema covers pagination and recursion controls. The description provides enough context to call the tool correctly, but it could more explicitly distinguish itself from project/item-level lookup siblings and qualify the 'all nested items' statement against recursive=false.

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 already explains bin_id, limit, offset, recursive, and max_depth. The description repeats the bin name/node ID lookup capability but adds no significant new parameter-level meaning. 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?

The description states a specific verb and resource ('Get detailed contents of a specific bin') and enumerates the returned data types: nested items, media paths, offline status, color labels, and metadata. It also clarifies search flexibility by bin name or node ID, making the tool's scope clear even among many sibling tools.

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

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool versus alternatives such as list_project_items, get_item_info, or search_project_items. The description implies usage through its title and content but does not state when-not-to-use or name relevant sibling tools.

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

Deploy Server