Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_channel_playlists

Fetch all playlists from a YouTube channel using its ID, @handle, /c, /user, or full URL. Returns playlist IDs, titles, video counts, thumbnails, and continuation tokens.

Instructions

Retrieve the playlists tab for a YouTube channel. Lists the playlists on a YouTube channel's Playlists tab. id accepts a channel id, @handle, /c or /user path, or a full channel URL. Each item has its playlist id, title, video count, thumbnail and URL. Pass the returned continuation_token back as continuation_token to get the next page.

Input Schema

NameRequiredDescriptionDefault
idYesChannel ID, @handle, /c path, /user path, or full YouTube channel URL
continuation_tokenNoPagination token returned by a previous request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses output fields (playlist id, title, video count, thumbnail, URL) and pagination mechanism (continuation_token), which are useful behavioral details. However, it omits authentication requirements, rate limits, and whether the operation is read-only (though implied by 'Retrieve' and 'Lists').

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?

Three sentences, but the first two are redundant ('Retrieve the playlists tab' and 'Lists the playlists on a YouTube channel's Playlists tab'). Otherwise front-loaded and clear, but some waste reduces efficiency.

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 simple retrieval tool with no output schema and full parameter coverage, the description covers purpose, input formats, output fields, and pagination. Missing auth/error details are not critical for this public-data tool.

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 both parameters are already documented. The description essentially repeats the id format and adds the instruction to pass continuation_token back for the next page. This adds slight value beyond the schema but is largely redundant; baseline 3 is appropriate.

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 clear verb+resource: 'Retrieve the playlists tab' and 'Lists the playlists on a YouTube channel's Playlists tab.' It distinguishes from generic video listings by specifying playlists. However, it does not explicitly differentiate from sibling tools like youtube_channel_videos or youtube_playlist.

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

Usage Guidelines2/5

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

No explicit when-to-use or alternatives are provided. The description implies usage for obtaining channel playlists but doesn't mention when to choose this over related tools (e.g., youtube_channel_videos or youtube_playlist).

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