Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel

Fetch YouTube channel details and stats using a channel ID, handle, or URL. Supports cached responses to reduce credit usage and returns public channel data for verification or research.

Instructions

youtube: Channel Details. GET /v1/youtube/channel. Provide one of: channelId, handle, url. Get YouTube channel details and stats by channelId, handle, or URL. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoYouTube channel URL. Provide channelId, handle, or url.
handleNoYouTube channel handle. Provide channelId, handle, or url.
channelIdNoYouTube channel ID. Provide channelId, handle, or url.
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.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well on cost behavior: 1 credit on success, free for errors, blocked or timed-out requests, invalid requests and cache hits, with not-found charged per published cost. It omits any auth requirements, rate limits, or return-shape hints, which keeps it short of 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.

Conciseness3/5

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

The identifier list appears twice (once as 'Provide one of: channelId, handle, url' and again in the following sentence), and the 'youtube: Channel Details. GET /v1/youtube/channel.' preamble repeats the name and route. The cost sentence is long but earns its place; the duplication does not.

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?

For a read tool with no output schema and no annotations, the description covers invocation and pricing but never indicates what 'details and stats' actually contains or whether the response is a single object. Auth expectations are also unstated, leaving real gaps for a tool whose output the agent must interpret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuinely additive rule the schema does not enforce: exactly one of channelId, handle, or url must be provided (the schema marks none required). It also frames cache_max_age as a zero-credit path, reinforcing the schema's wording.

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 specific verb and resource: 'Get YouTube channel details and stats by channelId, handle, or URL', plus the underlying route. It is clearly distinct from siblings such as youtube_channel_videos or youtube_channel_community_posts by virtue of returning channel-level data, though it never explicitly states that contrast.

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?

The only usage rule given is the identifier requirement ('Provide one of: channelId, handle, or url'), which is a calling constraint rather than when-to-use guidance. There is no mention of when to prefer youtube_channel_search or youtube_search over a direct lookup, so the agent must infer the boundary.

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