Skip to main content
Glama

Check a video's SEO

video_check
Read-onlyIdempotent

Use to audit one YouTube video for search and AI visibility. Returns twelve checks against the video anchor model (metadata, chapters, captions and storyboard where observed), each naming what it read and whether it passed. Read-only; results are cached for six hours unless fresh is true. For a channel's upload list use video_channel; for how a website embeds its videos use video_site.

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": {
      "v": "<v>"
    },
    "name": "video_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
vYesVideo id or URL
freshNoBypass the six-hour cache

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses caching behavior ('results are cached for six hours') and how to bypass it, plus what the response contains ('twelve checks ... each naming what it read and whether it passed'). This is substantive behavioral context rather than a restatement of the hints.

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 sentences, front-loaded with the action, then the return shape, then the sibling routing. Each sentence carries distinct information and none is padding.

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?

There is no output schema, but the description compensates by characterizing the twelve-check result structure and what each check reports. Caching, read-only nature, and alternatives are all covered, so an agent has everything needed to call 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?

Schema coverage is 100%, so both parameters (v, fresh) are already documented, and baseline 3 applies. The description reinforces the single-video scope of 'v' and the cache-bypass meaning of 'fresh', but adds no syntax or format detail the schema does not already carry.

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 ('audit one YouTube video') plus the scope ('search and AI visibility'), and immediately separates itself from video_channel and video_site. An agent can tell what this does without opening the 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?

Explicit routing is provided: 'For a channel's upload list use video_channel; for how a website embeds its videos use video_site.' The alternative tools are named with the condition that selects each, leaving little to inference.

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.