Skip to main content
Glama

Get Project Item Info

get_project_item_info
Read-onlyIdempotent

Retrieve detailed metadata and status for a Premiere Pro project item, including media path, resolution, duration, frame rate, codec, in/out points, offline state, and proxy status.

Instructions

Get detailed information about a project item (media file in the project panel): media path, resolution, duration, frame rate, codec info, metadata, color label, offline status, in/out points, and proxy status.

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": {
      "item_id": "<item_id>"
    },
    "name": "get_project_item_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item, or the sequence ID of a sequence
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the returned field set (media path, codec, offline status, proxy status, in/out points), which is useful context, but says nothing about cost, failure modes, or behavior when the item is offline/missing. With annotations doing the heavy lifting, a 3 fits.

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?

A single front-loaded sentence with zero filler; the resource is stated before the field list. The eleven-item enumeration is long but each element is informative, though it could have been grouped or trimmed to keep the sentence scannable.

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?

With an output schema present, the description needn't explain return structure, and annotations cover safety; the field list plus schema-level parameter docs make the definition usable as-is. The remaining gap is disambiguation from the many similar inspection siblings and any note on behavior for offline/relinked items.

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% and the nested CEP guard parameters are thoroughly documented in the schema itself. The description adds only the implicit object of interest ('a project item') and omits the fact that item_id also accepts a name or sequence ID and does not explain the expected_cep_target / expected_project_path guards. Baseline 3 applies since the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('get detailed information about a project item'), clarifies that the item is a media file in the project panel, and enumerates the returned fields. However, it never distinguishes itself from close siblings like get_item_info, get_full_clip_info, or inspect_project_item_av_metadata, which an agent cannot disambiguate from this text.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no routing to alternative tools. The field enumeration only indirectly implies the tool's purpose; an agent facing a dozen overlapping item-inspection siblings gets no help choosing this one.

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