Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Remove project item (bin)

premiere_remove_project_item
Destructive

Delete a bin from a Premiere Pro project by its nodeId. Confirmation is mandatory to prevent irreversible removal. Obtain nodeId from the list project items tool.

Instructions

Delete a BIN from the project by nodeId. Irreversible -> requires confirm:true. (Individual clips cannot be deleted via the stable DOM; do that in the Premiere UI.) Get nodeIds from premiere_list_project_items.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>"
    },
    "name": "premiere_remove_project_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesnodeId of the bin to delete (from list/find tools).
confirmNoMust be true to proceed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already signal destructiveness, but the description adds the explicit 'Irreversible' qualifier and the confirm requirement, providing additional behavioral context beyond the annotation.

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 concise sentences, front-loaded with primary action, and no extraneous information. Every sentence provides necessary guidance.

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?

For a simple destructive tool with two parameters, the description covers purpose, usage, requirements, limitations, and data source. No gaps given the annotations and input schema.

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%. The description repeats the schema definitions for nodeId and confirm without adding new meaning, so it meets but does not exceed the baseline.

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 uses a specific verb ('Delete') and resource ('BIN'), and clarifies it cannot delete individual clips, distinguishing it from any hypothetical sibling remove/delete tools and setting correct expectations.

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

Usage Guidelines5/5

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

Explicitly states the tool is irreversible and requires confirm:true, directs users to premiere_list_project_items for nodeId, and warns that individual clips cannot be deleted via the stable DOM, guiding users away from misuse.

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