Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_channel_playlists

Retrieve playlists from a YouTube channel using a channel ID or handle, and page through results with continuation tokens.

Instructions

youtube: Channel Playlists. GET /v1/youtube/channel/playlists. Provide one of: channelId, handle, continuationToken. Get playlists from a YouTube channel. Can pass channelId or handle. 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_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoYouTube channel handle
channelIdNoYouTube channel ID
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

A3.8/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 deliver: it discloses the cost model (1 credit on success, no charge for errors/blocked/timeout/invalid/cache hits) and explains pagination via the previous response's continuationToken. It omits any auth or quota/rate-limit context and says nothing about what a result contains.

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 core purpose and identifier constraint come first, followed by cost and pagination notes. The billing sentence is long and somewhat boilerplate-heavy, but each clause carries operational meaning.

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-optional-parameter read endpoint with no output schema, it covers invocation, pagination, and billing adequately. Missing links are response shape (handled implicitly by the absent output schema) and any authorization/scope notes.

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 real constraint beyond the schema: the three identifiers are alternatives ('provide one of'), and the continuationToken is tied to a prior response. That meaningfully reduces misuse risk.

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 and resource: 'Get playlists from a YouTube channel', which cleanly separates it from siblings like youtube_channel_videos or youtube_playlist. It does not explicitly name a sibling to contrast against, keeping it just below the top mark.

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?

'Provide one of: channelId, handle, continuationToken' gives an invocation constraint but no when-to-use versus alternatives (e.g. versus youtube_playlist for a single playlist) and no indication of which operation to pick for other channel content.

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