Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_video_sponsors

Infers possible sponsors for a YouTube video from public evidence and returns likely sponsor details; results are inferred, not an official YouTube sponsor field.

Instructions

youtube: Video Sponsors. GET /v1/youtube/video/sponsors. Experimental: infer possible video sponsors from public evidence, not an official YouTube sponsor field. 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_sponsors"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video or short URL
languageNoTwo-letter language code for transcript lookup, such as en, es, or fr.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 does substantial work: it discloses the credit cost (1 on success), the free cases (errors, blocked/timeouts, invalid requests, cache hits), and the not-found caveat. It omits auth requirements, rate limits, and what the inferred result actually contains, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with name, route, and the critical experimental caveat, followed by the cost model. Every sentence carries decision-relevant information; nothing is redundant padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A two-parameter tool with no annotations and no output schema needs the description to sketch the return shape, and this one does not say what sponsor evidence looks like (timestamps, confidence, names). Purpose and cost are covered well, but the caller is guessing about the result.

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%, so the schema already documents both url and language. The description adds nothing about either — notably it never explains that language drives transcript lookup, which is the mechanism behind the inference.

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?

States a specific verb+resource — inferring possible video sponsors from public evidence — and explicitly disclaims that this is not an official YouTube sponsor field. That experimental framing separates it from metadata siblings like youtube_video, though no sibling is named directly.

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: call it when you want sponsor information for a video URL. The 'Experimental' qualifier usefully signals results are heuristic, but there is no explicit when-not guidance and no pointer to a more authoritative alternative such as youtube_video or youtube_video_transcript.

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