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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get active sequence

premiere_get_active_sequence
Read-only

Retrieve details of the active sequence in Premiere Pro. Returns null if no sequence is active.

Instructions

Return details of the currently active sequence, or null if none is active. 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_get_active_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotation already declares readOnlyHint=true. The description additionally states 'Read-only' and clarifies the null case, which adds value beyond the annotation. No contradictions.

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?

The description is a single sentence that is front-loaded and contains no extraneous words. Every word earns its place.

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

Completeness4/5

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

For a read-only, zero-parameter tool, the description adequately communicates the return value (sequence details or null). The lack of an output schema is mitigated by the simple nature of the 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?

The input schema has 0 parameters, and schema coverage is 100%. The description does not need to add parameter info. Baseline 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 clearly states the tool returns details of the currently active sequence or null, with a specific verb and resource. It is easily distinguished from siblings like 'premiere_list_sequences' (lists all sequences) and 'premiere_set_active_sequence' (sets active sequence).

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 context of 'active sequence' implies when to use this tool. It does not explicitly provide when-not or alternatives, but the purpose is clear enough for an AI agent to decide. No exclusions are needed.

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