Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_sequence_from_preset

Generates a sequence in Adobe Premiere Pro from a preset, applying predefined settings for quick project setup. Specify the preset to match your editing requirements.

Instructions

Premiere Pro expanded operation: create sequence from preset.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.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. However, it only restates the name and gives no information about side effects, required permissions, or what happens when the operation executes—leaving the agent completely uninformed.

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 minimal and concise, but it is under-specified to the point of uselessness. It lacks any structured detail or front-loaded information that would aid decision-making, so brevity doesn't earn credit.

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 output schema, no annotations, and a permissive but ambiguous input schema, the description provides virtually no context. The tool likely requires knowledge of preset settings and parameters, but none of that is disclosed, making it incomplete for any real-world use.

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 defines zero explicit parameters but allows arbitrary additional properties, making the schema effectively uninformative. The description adds nothing about what parameters (like preset name or file path) are expected, leaving the agent without any guidance on how to invoke the operation correctly.

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

Purpose2/5

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

The description 'Premiere Pro expanded operation: create sequence from preset' essentially restates the tool name without providing specific details on what constitutes a preset or how it differs from similar tools like create_sequence or create_sequence_from_clips. It lacks a clear verb-resource-object structure and offers no distinction from 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 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 other sequence creation tools, no mention of prerequisites, and no exclusions or alternatives. The description fails to give any context for appropriate usage.

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