Premiere Pro MCP Server

Get Bin Contents

get_bin_contents

Read-onlyIdempotent

Retrieve detailed contents of a Premiere Pro bin, including nested items, media paths, offline status, color labels, and metadata. Search by bin name, node ID, or path.

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'); '/' or 'root' for the project root
`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; 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
```

changedInput schema / properties / bin_id / description

Previous value: -"Bin name, node ID, or path (e.g., 'Footage', 'Footage/Raw')"New value: +"Bin name, node ID, or path (e.g., 'Footage', 'Footage/Raw'); '/' or 'root' for the project root"

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

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

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful content scope ('all nested items, media paths, offline status, color labels, and metadata'), but does not go beyond structured data to describe pagination behavior, recursion defaults, or response shape.

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 compact sentences, front-loaded with the tool action and followed by addressing syntax. Every phrase earns its place, with no redundancy or filler.

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?

Given the rich input schema, existing output schema, and strong annotations, the description covers the essential purpose and lookup method. It leaves pagination, recursion defaults, and output details to structured fields, which is reasonable, though an explicit sibling distinction could improve completeness.

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 input schema already documents bin_id, limit, offset, max_depth, and recursive in detail. The description's 'Searches by bin name or node ID' only partially mirrors the schema's richer bin_id description and adds no parameter meaning beyond it.

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?

The description states a specific verb and resource: 'Get detailed contents of a specific bin (folder)' and lists the returned item types. This clearly identifies what the tool does, though it does not explicitly distinguish itself from adjacent siblings such as list_project_items or get_project_item_info.

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?

The phrase 'Searches by bin name or node ID' implies when the tool is useful and how to address a bin, but there is no explicit when-to-use guidance, prerequisites, or named alternative. Usage is inferable but not spelled out.

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

Deploy Server