Skip to main content
Glama

video_info

Read-onlyIdempotent

Probe a video file to retrieve duration, resolution, codec, fps, and size as JSON before editing, so you can confirm the source's dimensions and length.

Instructions

Probe a video file for metadata. Returns JSON {success, info:{duration, resolution, codec, fps, size, ...}}. Use before any edit to learn the source's dimensions and length.

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

Input Schema

NameRequiredDescriptionDefault
exactNoAlso report decoded frame_count, frame_count_source, r_frame_rate and avg_frame_rate (null when not measurable). Slower: decodes the whole stream.
input_pathYesAbsolute path to the video file.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / exact / description
      Added value: +"Also report decoded frame_count, frame_count_source, r_frame_rate and avg_frame_rate (null when not measurable). Slower: decodes the whole stream."
    • removedInput schema / properties / exact / title
      Removed value: -"Exact"
    • addedInput schema / properties / input_path / description
      Added value: +"Absolute path to the video file."
    • removedInput schema / properties / input_path / title
      Removed value: -"Input Path"
    • removedInput schema / properties / overwrite
      Removed value: -{
      -  "default": false,
      -  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
      -  "title": "Overwrite",
      -  "type": "boolean"
      -}
    • removedInput schema / title
      Removed value: -"video_infoArguments"
    • removedOutput schema / title
      Removed value: -"video_infoDictOutput"
  2. Changed1 schema field changedv1.16.5
    • addedInput schema / properties / exact
      Added value: +{
      +  "default": false,
      +  "title": "Exact",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
      +  "title": "Overwrite",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  5. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the return envelope ({success, info:{...}}) and the pre-edit sequencing advice, but says nothing about failure behavior (e.g., what happens on a missing/corrupt file) or cost, so it is useful but not rich beyond the annotations.

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?

Three tight sentences: purpose first, return shape second, usage guidance last. No filler, and the most decision-relevant information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only probe with an output schema, this covers what it does, what comes back, and when to call it. Nothing an agent needs to invoke it correctly is missing.

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%: input_path (absolute path) and exact (decode full stream for accurate frame counts, slower) are already documented in the schema. The description's mention of dimensions and length maps to output fields rather than parameter behavior, so it adds nothing new about the two parameters. 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?

"Probe a video file for metadata" gives a specific verb and resource, and the return-shape hint names the concrete fields (duration, resolution, codec, fps, size). It does not explicitly distinguish itself from diagnostic siblings such as video_doctor or video_qc_ops, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use before any edit to learn the source's dimensions and length" gives a clear triggering context and implicitly rules out using it after editing. There are no named alternatives or when-not conditions, which keeps it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.