Skip to main content
Glama

Video Info

video-info
Read-only

Extract video metadata, available formats, and thumbnail from any URL. Returns the title, duration, thumbnail, uploader, upload date, view count, platform and the available formats with their sizes. Use to inspect a video before downloading it. To get the file use video-download; for what is said in it use transcribe. Cost: 1 credit, charged only when a call succeeds.

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": {
      "url": "<url>"
    },
    "name": "video-info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the video or post containing a video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive behavior, so the description's extra value is the cost model ('1 credit, charged only when a call succeeds') and the returned metadata fields. It does not cover failure/error behavior or rate limits, so it is strong but not exhaustive.

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?

The description is front-loaded with purpose and return values, then usage/alternatives, then cost. It repeats 'thumbnail' and 'available formats' between the first two sentences, but the repetition is minor and does not obscure the call.

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 simple one-parameter read tool with no output schema, the description supplies the key return fields and the success-based credit behavior. Annotations cover the safety profile, so an agent has enough context to invoke it correctly.

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?

The single parameter has 100% schema description coverage ('URL of the video or post containing a video'), and the description adds little beyond 'any URL'—no format, validation, or platform-specific syntax. Baseline 3 applies because the schema already carries parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Extract video metadata, available formats, and thumbnail') and names the concrete return fields. It also distinguishes itself from video-download and transcribe, so the agent can select it without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly says 'Use to inspect a video before downloading it' and names alternatives: video-download for the file and transcribe for spoken content. This gives both the when-to-use condition and the main alternative routes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.