Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

insert_from_source

Inserts a chosen source clip into the active Premiere Pro sequence, letting editors add media from a source panel or bin directly to the timeline.

Instructions

Premiere Pro expanded operation: insert from source.

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": "insert_from_source"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention what the operation does (e.g., places a clip from the source monitor into a sequence), any side effects, or constraints. It is wholly uninformative.

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 a single vague sentence, but this is under-specification rather than conciseness. It does not front-load any useful information and wastes the opportunity to provide essential context.

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?

Given the complexity of a Premiere Pro editing operation, with no annotations, no output schema, and an empty input schema, the description fails entirely to explain the tool's purpose, behavior, or usage. It is completely inadequate for an agent to select or invoke this tool correctly.

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

Parameters2/5

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

The input schema has zero defined parameters (only an empty object with additionalProperties), so there is nothing to explain. The description adds no parameter-related information and does not compensate for the lack of schema details or clarify how the operation is invoked. While 0 params typically allows a baseline of 4, the description contributes no semantic value whatsoever.

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: insert from source.' is essentially a restatement of the tool name. It provides no specific verb+resource beyond the name itself and fails to distinguish this from sibling tools like 'overwrite_from_source' or 'open_in_source'.

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. The description gives no context about prerequisites, editing workflows, or scenarios where insertion from source is preferred over other operations.

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