Skip to main content
Glama

Inspect a video source

video_info

Retrieve duration, dimensions, codec facts, cache statistics, and configured limits for a local video or public YouTube URL without model calls or uploads.

Instructions

Report duration, dimensions, codec facts, cache statistics, and the configured limits for a local video or public YouTube URL. No model call and no upload.

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": {
      "source": "<source>"
    },
    "name": "video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Output Schema

NameRequiredDescriptionDefault
fpsNo
notesNo
widthNo
heightNo
limitsYes
has_audioNo
mime_typeNo
size_bytesNo
source_kindYes
canonical_idYes
cached_analysesNo
duration_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: no model invocation and no upload (i.e., non-destructive, cheap, read-only). It omits what happens for a non-public or invalid YouTube URL, whether results are cached/refreshed, and any auth requirements, which matters for the URL path.

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 sentences, no filler, with the returned content front-loaded and the cost/behavior caveat trailing as a compact qualifier. Every clause carries distinct information.

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 the enumerated return fields need not be fully specified here, and the description still names the categories of output. For a single-parameter inspect tool this is nearly complete; only failure modes for inaccessible sources are left uncovered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single 'source' parameter, so the description must compensate, and it does by defining the accepted value space: a local path or a public YouTube URL. The 'public' qualifier is a real constraint not present in the schema, though path format and relative-vs-absolute conventions remain unstated.

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 ('Report') and enumerates the resource facts it returns (duration, dimensions, codec, cache stats, limits) for a local video or public YouTube URL. It implicitly separates itself from analyze_video via 'No model call and no upload', but never names an alternative explicitly, so differentiation is inferential rather than declared.

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 phrase 'No model call and no upload' plus the accepted source types implies this is the cheap metadata-only entry point before heavier siblings like analyze_video or extract_frames, but no when-to-use or when-not-to-use condition is stated. The agent has to infer the routing rule from the cost hint.

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