Skip to main content
Glama

Check a site's video pages

video_site
Read-onlyIdempotent

Use to check how a website carries its videos. Reads the homepage plus up to 60 sitemap pages for YouTube embeds, facades and page-builder widgets, VideoObject nodes and their required properties, and, given a channel handle, how many of the channel's videos the site carries. Read-only. For one video use video_check; for a channel's uploads use video_channel.

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": {
      "domain": "<domain>"
    },
    "name": "video_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is free; the description still adds real behavioral context beyond them by disclosing the crawl footprint (homepage + up to 60 sitemap pages) and what it examines. It stops short of stating runtime, rate limits, or what happens when a site has no sitemap, which keeps it off a 5.

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?

Three sentences, zero preamble, capability scoped up front and the sibling routing placed last where it reads as a hand-off. The middle sentence is a long list of detection targets, but each item is substantive rather than filler.

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?

No output schema exists, yet the description makes the return content inferable (embed types, VideoObject property coverage, channel carry count) and defines the crawl bounds an agent needs to reason about cost. A brief note on behavior when the site lacks a sitemap or on result shape would close the remaining gap.

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 coverage is 0% with two parameters, so the description carries the burden; it does identify the role of both (domain = the site being checked, handle = the channel whose video count is measured), which is genuine added meaning. It gives no syntax for handle (e.g. with or without @) and never explicitly ties "domain" to the required field, leaving a gap for a 0%-coverage schema.

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 ("check how a website carries its videos") and immediately scopes it with a concrete crawl ("homepage plus up to 60 sitemap pages") and the signals it inspects (YouTube embeds, facades, VideoObject nodes). It explicitly names the siblings it is not (video_check, video_channel), so an agent can route correctly without opening a schema.

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?

Gives explicit routing rules: "For one video use video_check; for a channel's uploads use video_channel." The optional-handle path is also described as a distinct mode (count how many of a channel's videos the site carries), so when-to-use is fully covered.

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.