Skip to main content
Glama

Get video info

get_video_info
Read-only

Title, uploader, duration, thumbnail and available qualities of a public video link (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick). Posts with several videos list each one as an item.

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": "get_video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo)."New value: +"Link to a public post or video (YouTube, Instagram, X / Twitter, TikTok, Bluesky, Facebook, VK, LinkedIn, Weibo, Twitch, Kick)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: only public links are accepted, and posts containing multiple videos return one item per video, which shapes how the agent must parse results. It does not cover private/deleted link failure behavior, but for a pure read that is a minor omission.

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?

Two tight sentences: the first front-loads the returned fields and scope, the second handles the multi-video edge case. The platform enumeration appears in both the description and the schema, which is slight redundancy, but no sentence is wasted.

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?

With only one required parameter and no output schema, the description usefully compensates by listing the fields returned and by warning that multi-video posts flatten into items. That is close to complete for this complexity; the only missing piece is what happens on unsupported or non-public links.

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% for the single url parameter, and the schema already enumerates the supported platforms. The description restates that platform list and adds only 'public post or video', so it does not meaningfully extend the schema's semantics. Baseline 3 applies when the schema does the documentation work.

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?

The description names a concrete verb-resource pairing by enumerating exactly what is returned — title, uploader, duration, thumbnail, available qualities — for a public video link, and lists the supported platforms. It is clearly distinct from media-fetching siblings like download_video or get_transcript without naming them. It stops short of an explicit differentiator sentence, so a 4 rather than 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 Guidelines3/5

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

Usage is implied by the word 'public' and by the fact that it only returns metadata, which lets an agent infer this is the pre-flight lookup before download_video or get_transcript. However, there is no explicit when-to-use or when-not-to-use statement, no mention of private/unavailable links failing, and no named alternative.

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.

Resources