Skip to main content
Glama

Inspect Project Item Av Metadata

inspect_project_item_av_metadata
Read-onlyIdempotent

Inspect a project item's documented effective and original color space, LUT IDs, available color-space overrides, and audio channel shape to verify media settings before editing.

Instructions

Inspect a project item's documented effective/original color space, LUT IDs, available color-space overrides, and audio channel shape.

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

Input Schema

NameRequiredDescriptionDefault
item_idYesProject item node ID or exact name, 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/idempotent/non-destructive, so the safety profile is covered and the description only needs to add substance. The word 'documented' hints that values are host-reported rather than measured, which is mild but real added context; however nothing is said about failure modes when an item has no LUT or no audio channels, or about the CEP-only guard the schema mentions.

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 dense sentence with zero filler, front-loading the verb and the returned fields. It is efficient, though the comma-separated field list reads as a spec dump rather than being organized by category (color vs audio).

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?

Read-only inspection with full annotations, an output schema, and 100% schema coverage — the description only needs to state scope, which it does. The remaining gap is orientation against the many sibling inspection/color tools, which limits selection confidence.

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%, so item_id and the optional expected_cep_target/expected_project_path guards are fully documented in the schema, including that UXP refuses the CEP-only guard. The description adds no further parameter meaning, so baseline 3 applies.

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?

Precise verb ('Inspect') plus resource ('a project item's ... metadata') and an explicit enumeration of the fields surfaced: effective/original color space, LUT IDs, color-space overrides, audio channel shape. An agent knows exactly what comes back, but the description never distinguishes this from overlapping siblings such as get_color_space, get_clip_properties, or inspect_sequence_av_settings.

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?

It says nothing about when to reach for this versus the color-space or clip-property siblings, nor any precondition (item must be resolvable, CEP backend required). Usage must be inferred entirely from the name and the field list.

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