Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_video

Fetch YouTube video or Short details—description, owner identity, paid-promotion status, and replay heatmaps—from a URL to verify content and analyze performance.

Instructions

youtube: Video/Short Details. GET /v1/youtube/video. Get YouTube video or Short details, description cards, AI disclosures, owner/uploader identities, paid-promotion status and replay heatmaps. Age-restricted videos return 403. No hosted video downloads. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video or short URL
languageNoPreferred two-letter response language, such as en, es, or fr. Sets Accept-Language; YouTube may ignore it.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it discloses the 403 age-restriction behavior, the absence of video downloads, and a detailed credit model (1 credit on success; errors, blocked, timed-out, invalid requests and cache hits free). It stops short of describing required auth or response shape, which keeps it below 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?

Purpose and returned data are front-loaded, followed by constraints and billing in a compact sequence. The billing sentences are somewhat dense and could be trimmed, but each conveys a distinct, non-obvious rule.

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?

For a three-parameter read tool with no output schema, the definition covers purpose, returned fields, error behavior, and cost model adequately. A brief note on response format or auth requirements 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 100% and all three parameters are already documented in the schema, so the baseline applies. The description reinforces credit/caching semantics that relate to cache_max_age, but adds no new meaning about url formats or language handling beyond what the schema states.

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?

"Get YouTube video or Short details" names a specific verb and resource, and the enumeration of returned content (description cards, AI disclosures, uploader identities, paid-promotion status, replay heatmaps) sharply separates it from sibling tools such as youtube_video_transcript and youtube_video_comments. An agent can tell what this tool yields 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 Guidelines3/5

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

Usage is implied by the data it returns, but there is no explicit "use this when..." routing versus siblings like youtube_video_sponsors (paid promotion) or youtube_video_transcript. Some negative guidance is present ("No hosted video downloads", age-restricted videos return 403), which helps exclude impossible calls but does not direct choice among alternatives.

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

Deploy Server

Other Tools