Skip to main content
Glama

Analyze Video Qc

analyze_video_qc

Scan a local video with FFmpeg to report sustained black frames and frozen sections, including duration and location, without contacting Premiere or modifying the file.

Instructions

Analyze a local video delivery for sustained black and frozen sections with FFmpeg. Read-only: it does not contact Premiere or modify the file.

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": {
      "media_path": "<media_path>"
    },
    "name": "analyze_video_qc"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_pathYesPath to an existing local video file
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.
minimum_black_secondsNoMinimum black duration to report (default: 0.5)
minimum_freeze_secondsNoMinimum frozen duration to report (default: 1)

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.4/5.0
Behavior2/5

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

The description adds real behavioral context beyond the schema — it names the detection method (FFmpeg), states it does not contact Premiere, and states it does not modify the file. However, 'Read-only' directly conflicts with the annotation readOnlyHint=false, leaving the agent with two contradictory safety signals, and no mention is made of cost/runtime on long media or how many defects are returned.

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 short sentences with zero filler: the capability first, the safety constraint second. Every clause carries information an agent cannot get from the name alone.

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 values need no explanation, and the 100%-covered input schema handles parameters. Given the tool's low complexity, the description covers purpose, engine and non-mutation adequately; only the read-only vs. readOnlyHint=false discrepancy and the absence of any note about FFmpeg being a local dependency leave gaps.

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 media_path, both duration thresholds (defaults 0.5s / 1s) and the envelope fields. The description adds nothing about the thresholds — that black/freeze detection is tunable via the two minimum_*_seconds parameters — so it sits at the baseline.

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 ('Analyze a local video delivery') plus the exact defect classes it detects ('sustained black and frozen sections') and the engine ('FFmpeg'). This implicitly separates it from scope/loudness/interlacing siblings (e.g. read_video_scopes, analyze_loudness) by defect type, but no alternative tool is ever named.

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 by 'local video delivery' and the read-only caveat, which tells the agent this is safe to run on a file without Premiere being open. There is no explicit when-to-use/when-not guidance, no prerequisite (FFmpeg availability) and no routing to analyzer siblings, so the agent must infer the context.

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