Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_playlist

Retrieve a paginated list of videos from a YouTube playlist using its playlist ID; pass the continuation token to fetch subsequent pages.

Instructions

youtube: Playlist. GET /v1/youtube/playlist. Provide one of: playlist_id, continuationToken. Get a paginated list of videos in a YouTube playlist 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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "youtube_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYesThe ID of the YouTube playlist. In the YouTube URL it will be the 'list' parameter.
continuationTokenNoToken from the previous response to get the next page. Omit for the first page. Stop when the returned continuationToken is null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 it discloses billing behavior in detail: 1 credit on success, free for errors, blocked, timed-out, invalid, and cache hits. It omits auth requirements and rate limits, and does not describe the shape of returned video objects, but the cost semantics are unusually explicit.

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 purpose is front-loaded correctly, but the billing explanation spans three sentences with hedging ("charged only where that operation's published cost says so") that could be compressed. The result reads as a route listing plus a cost policy rather than a tight tool description.

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?

It covers purpose, pagination, and cost, with no output schema to explain return values beyond the paginated-video framing. However, for a data-returning list endpoint it does not characterize what a video entry contains, and the 'one of' constraint muddies whether playlist_id is required.

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%, so the schema already explains playlist_id (the 'list' URL parameter) and continuationToken pagination. The description adds little beyond that. Worse, "Provide one of: playlist_id, continuationToken" conflicts with the schema's required playlist_id, adding ambiguity rather than meaning.

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 states a specific verb and resource: "Get a paginated list of videos in a YouTube playlist," plus the underlying route GET /v1/youtube/playlist. An agent can distinguish this from channel-level playlist tools. It does not explicitly name or contrast a sibling, keeping it from a 5.

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 only implied by the phrase "Get a paginated list of videos in a YouTube playlist." There is no stated when-to-use versus alternatives (e.g., youtube_channel_playlists or youtube_search) and no prerequisites. The one-detail given, "Omit for the first page," is parameter guidance rather than tool selection guidance.

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