Skip to main content
Glama

pr_catalog

Lists available Premiere Pro operations and their parameters by category, so you can check what an operation needs before calling it.

Instructions

List Premiere Pro operations available through pr_do. Without category: categories with counts and operation names. With category: every operation of that category with its parameters. Call it before using an operation you have not used in this session. Clips are addressed by node_id from pr_get_sequence.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoadvanced | after_effects | audio | av_settings | captions | clipboard | context | delivery | dialogue | discovery | edit_plans | effects | export | health | inspection | intake | interchange | keyframes | markers | masks | media | media_analysis | metadata | mogrt | playback | playhead | project | project_manager | recovery | review | scripting | selection | sequence | shorts | source_monitor | text | timeline | timeline_qa | track_targeting | tracks | transcript | transitions | utility | uxp | workflows | workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / category / description
      Previous value: -"advanced | after_effects | audio | av_settings | captions | clipboard | context | delivery | dialogue | discovery | edit_plans | effects | export | health | inspection | intake | interchange | keyframes | markers | media | media_analysis | metadata | mogrt | playback | playhead | project | project_manager | recovery | review | scripting | selection | sequence | shorts | source_monitor | text | timeline | timeline_qa | track_targeting | tracks | transcript | transitions | utility | uxp | workflows | workspace"New value: +"advanced | after_effects | audio | av_settings | captions | clipboard | context | delivery | dialogue | discovery | edit_plans | effects | export | health | inspection | intake | interchange | keyframes | markers | masks | media | media_analysis | metadata | mogrt | playback | playhead | project | project_manager | recovery | review | scripting | selection | sequence | shorts | source_monitor | text | timeline | timeline_qa | track_targeting | tracks | transcript | transitions | utility | uxp | workflows | workspace"
  2. Changed2 schema fields changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / category / description
      Previous value: -"advanced | after_effects | audio | av_settings | captions | clipboard | context | delivery | dialogue | discovery | edit_plans | effects | export | health | inspection | intake | interchange | keyframes | markers | media | media_analysis | metadata | mogrt | playback | playhead | project | project_manager | recovery | scripting | selection | sequence | shorts | source_monitor | text | timeline | timeline_qa | track_targeting | tracks | transcript | transitions | utility | uxp | workflows | workspace"New value: +"advanced | after_effects | audio | av_settings | captions | clipboard | context | delivery | dialogue | discovery | edit_plans | effects | export | health | inspection | intake | interchange | keyframes | markers | media | media_analysis | metadata | mogrt | playback | playhead | project | project_manager | recovery | review | scripting | selection | sequence | shorts | source_monitor | text | timeline | timeline_qa | track_targeting | tracks | transcript | transitions | utility | uxp | workflows | workspace"
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the return shape in both modes (categories with counts and operation names vs. full parameter listings) and clarifies it is a discovery/read surface feeding pr_do. It doesn't explicitly state read-only/side-effect-free status or caching behavior, which keeps it from a 5.

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?

Front-loaded with the purpose, then the two behavioral modes, then the call trigger. Every sentence earns its place; the closing node_id note is a useful cross-reference rather than filler.

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?

One optional parameter and no output schema, so the description must explain return values — which it does for both branches. Nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is already 100% and the schema enumerates the valid category values, so the baseline is 3. The description goes beyond it by explaining the semantic effect of omitting versus supplying `category`, which is the key decision the agent must make.

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?

States a specific verb and resource (list Premiere Pro operations exposed via pr_do) and implicitly contrasts with pr_do itself, which executes rather than enumerates. An agent can distinguish this catalog tool from every sibling without opening a schema.

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?

"Call it before using an operation you have not used in this session" is a concrete, actionable trigger, and the two-mode description tells the agent how to scope the lookup. It stops short of naming an explicit alternative or a when-not condition beyond the session-cache hint.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.