Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

inspect_dom_object

Inspect any Premiere Pro DOM object by specifying a dot-path. Lists its properties, methods, and values to help explore the API and debug issues.

Instructions

Inspect a Premiere Pro DOM object and list its properties, methods, and values. Useful for exploring the API and debugging.

Examples:

  • "app.project" → project properties

  • "app.project.activeSequence" → sequence properties

  • "app.project.activeSequence.videoTracks[0].clips[0]" → first clip on V1

  • "app.project.activeSequence.videoTracks[0].clips[0].components[0]" → first component of a clip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_pathYesDot-path to the DOM object to inspect (e.g., 'app.project.activeSequence')
max_depthNoMax depth for nested inspection (default: 1, max: 3)
Behavior2/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. It states the tool inspects and lists, but does not disclose side effects, read-only nature, or performance implications. Limited behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with the main purpose, then provides examples. Every sentence adds value, though it could be slightly more concise.

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?

Without an output schema, the description does not explain the format or details of the returned information beyond 'properties, methods, and values'. More detail on the output structure would improve completeness.

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%, so both parameters are described in the schema. The description adds examples but no additional semantic meaning beyond the schema. 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 clearly states the tool inspects a Premiere Pro DOM object and lists properties, methods, and values. Examples show specific paths, distinguishing it from sibling tools that perform mutations or specific retrievals.

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

Usage Guidelines3/5

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

The description implies use for exploring the API and debugging, but does not provide explicit guidance on when to use versus alternatives or when not to use. No exclusion criteria are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leancoderkavy/premiere-pro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server