Skip to main content
Glama

Verify Fcpxml Media References

verify_fcpxml_media_references

Check whether file:// media references in FCPXML or FCP7 XML files resolve inside caller-approved existing roots; paths outside those roots are never inspected or exposed.

Instructions

Verify the file:// media references of an FCPXML or FCP7 XML (xmeml) document, only inside caller-approved existing roots. References outside those roots are never statted or exposed as local paths.

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": {
      "path": "<path>",
      "allowed_roots": "<allowed_roots>"
    },
    "name": "verify_fcpxml_media_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExisting local .fcpxml or .xml file
allowed_rootsYesOne to sixteen existing absolute roots that may be inspected
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
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

A3.6/5.0
Behavior3/5

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

The description adds real behavioral context beyond the annotations: out-of-root references are never statted and never surfaced as local paths, which tells the agent about a privacy/security boundary. However, with readOnlyHint=false declared on what is described as a verification operation, the description does not clarify what side effects, if any, occur, nor whether unresolved or out-of-root references are reported as findings or silently skipped. That is a meaningful gap for a tool whose name is 'verify'.

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?

Two tightly written sentences, front-loaded with the verb and resource, with the scoping restriction and its consequence following immediately. No filler, no restatement of the title, and the negative guarantee is stated compactly.

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?

An output schema exists, so return-shape explanation is unnecessary, and annotations plus full schema coverage carry most of the structured burden. The description covers purpose and the root-scoping boundary. What it leaves open is how out-of-root or missing references are surfaced in the result (violation vs. omission) and whether any state changes occur — the one thing an agent deciding to call it would still want.

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 the schema already documents path, allowed_roots, idempotency_key, expected_cep_target and expected_project_path in detail. The description reinforces allowed_roots semantics ('caller-approved existing roots') and the resulting non-exposure of out-of-root paths, but adds no new format, limit, or edge-case detail beyond the schema. 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?

States a specific verb (verify), a specific resource (file:// media references), and the document types it accepts (FCPXML or FCP7 xmeml). The scope constraint ('only inside caller-approved existing roots') further narrows it. It stops short of naming a sibling such as check_offline_media or inspect_fcpxml_interchange, so an agent must still infer when this differs from other verification tools.

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?

Usage is implied rather than stated: the agent can infer this is a pre-import/pre-delivery check of an XML document's media paths. There is no explicit when-to-use, no when-not, and no named alternative among the many verify_* siblings in the catalog. The root-scoping constraint is a boundary condition, not guidance on tool selection.

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