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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List sequence presets

premiere_list_sequence_presets
Read-only

Browse and filter available sequence presets from disk—HD 1080p, UHD, Broadcast—to select an exact preset for non-interactive sequence creation.

Instructions

List available .sqpreset sequence presets on disk (HD 1080p, UHD, Broadcast, etc.), optionally filtered. Pass a 'path' to premiere_create_sequence for an exact, non-interactive setup. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFilter by filename substring (e.g. '1080', '25 fps', 'UHD').
limitNoMax presets (default 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' is redundant. The description adds no additional behavioral details (e.g., what is returned, pagination, side effects). With annotations present, the bar is lower, but further context beyond safety would improve the score.

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 sentences with no wasted words. The purpose, filtering, and cross-reference to premiere_create_sequence are front-loaded and clear.

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 read-only listing tool with 100% schema coverage and no output schema, the description is complete. It explains what presets are listed, optional filtering, and how the output path is used by another tool.

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 schema fully documents both parameters (query and limit). The description adds no extra meaning beyond 'optionally filtered', so the baseline score of 3 is appropriate.

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 explicitly states the tool lists .sqpreset sequence presets on disk, giving examples like HD 1080p, UHD, and Broadcast. This clearly distinguishes it from sibling tools like premiere_list_export_presets (for export presets) and premiere_create_sequence (which uses the path).

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

Usage Guidelines4/5

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

The description mentions optional filtering and advises passing the path to premiere_create_sequence for non-interactive setup, providing good context. However, it does not explicitly state when not to use this tool or offer exclusions, which would merit a 5.

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