Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel_videos

Retrieve paginated videos from a YouTube channel by channel ID or handle, with sorting by latest or popular. Use continuation tokens to page through results.

Instructions

youtube: Channel Videos. GET /v1/youtube/channel-videos. Provide one of: channelId, handle. Get paginated videos from a YouTube channel by channelId or handle. Paid-promotion filtering is not supported; use /v1/youtube/video and its isPaidPromotion field for each video's status. 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_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by latest or popular
handleNoYouTube channel handle
channelIdNoYouTube channel ID
includeExtrasNoInclude like/comment counts and descriptions. Increases errors and may be deprecated; use /v1/youtube/video for full details.
continuationTokenNoUse continuationToken from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well on cost semantics: 1 credit on success, free failures, cache hits, and conditional charging for empty/not-found results. It does not cover authentication, rate limits, or what the returned video objects contain.

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?

The description is appropriately sized and every part is useful, especially the billing and alternative-endpoint details. The leading route/name fragments slightly delay the actual purpose, but the text remains efficient and readable.

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 five-parameter, read-only listing tool with no output schema, the description covers the core operational facts: channel identification, pagination via continuationToken, costs, and the paid-promotion workaround. It could be more complete by describing the returned video fields or whether shorts/lives are included.

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 an important constraint absent from the schema: one of channelId or handle must be supplied even though the schema lists no required parameters. It does not further clarify sort, includeExtras, or continuationToken beyond their schema descriptions.

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 gives a specific verb and resource: get paginated videos from a YouTube channel by channelId or handle. It distinguishes this from the video-level detail endpoint for paid-promotion status, but does not clarify its relationship to channel search, shorts, or live-video siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It explicitly states that one of channelId or handle must be provided and gives a clear when-not case: paid-promotion filtering is unsupported, so use /v1/youtube/video per video. It does not explain when to choose this over channel search, shorts, or live-video 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