Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_selected_clips

Retrieve all clips currently selected in a given Premiere Pro sequence by sequence ID, so you can target edits, effects, or exports to exactly the user's active selection.

Instructions

Gets all currently selected clips in the specified sequence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sequenceId": "<sequenceId>"
    },
    "name": "get_selected_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequenceIdYesThe ID of the sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry transparency. It clearly implies a read-only operation ('Gets') but does not disclose return format, whether it includes hidden clips, or if it depends on active state. This is minimal but not misleading, adequate for a simple getter.

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, focused sentence with no superfluous words. It is perfectly concise and front-loaded with the action.

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

Completeness3/5

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

For a getter with one parameter and no output schema, the description is minimal but sufficient to understand the core behavior. However, it lacks context about how selection is defined (e.g., does it include clips on all tracks?) and how the result is returned. Given the low complexity, it's barely adequate.

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 coverage is 100% for the single parameter (sequenceId), and the description adds no additional semantic information beyond what the schema provides. Baseline of 3 applies because the schema already documents the parameter adequately.

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 retrieves all currently selected clips within a specified sequence, using a specific verb ('Gets') and resource ('selected clips') with scope ('in the specified sequence'). This distinguishes it from sibling tools like select_clips_by_name or get_clip_at_playhead.

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

Usage Guidelines2/5

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

No guidance is given on when to use this vs alternatives. It does not mention exclusions or contexts (e.g., 'use this after making a selection' or 'prefer this over get_clip_at_playhead for multiple clips'). The purpose is implied but no explicit usage direction is provided.

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