Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

consolidate_and_transfer

Consolidate Premiere Pro project assets and transfer them to a new location, preparing projects for sharing or backup.

Instructions

Premiere Pro expanded operation: consolidate and transfer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consolidate_and_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.1/5.0
Behavior1/5

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

With no annotations, the description must disclose behavior, but it only states a phrase without details. It does not mention effects on project files, media, undoability, or any side effects. The agent is left completely in the dark.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is technically concise (one sentence), but it is so under-specified that it fails to convey any actionable information. It is not a tautology like 'process' but it's barely an expansion of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and an empty schema, the description is the sole source of information ROM an agent. It provides no details on inputs, outputs, side effects, or operational context. This is severely incomplete for a tool that likely performs a complex operation in Premiere Pro.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is essentially empty (an object with no defined properties), yet the tool is named 'consolidate and transfer' which implies at least some input (e.g., target location, items to consolidate). The schema provides no guidance, and the description doesn't clarify what parameters might be accepted or expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Premiere Pro expanded operation: consolidate and transfer' is essentially a label rather than a description. It names the tool but does not explain what 'consolidate' and 'transfer' mean in this context, nor does it distinguish it from siblings like consolidate_duplicates or export_aaf. The purpose is completely unclear.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No context about workflows, prerequisites, or scenarios is provided. The description is far too vague to help an agent decide when to invoke it.

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