Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_playlist

Retrieve YouTube playlist metadata and videos by playlist ID or full URL, including title, channel, video count, positions, durations, and views; page with continuation tokens.

Instructions

Retrieve playlist metadata and items. Returns a YouTube playlist by playlist id or full playlist URL: title, URL, owning channel, video count and thumbnail, plus its videos with position, title, video id, duration, channel and view count. Pass the returned continuation_token to page through longer playlists.

Input Schema

NameRequiredDescriptionDefault
idYesYouTube playlist ID or full playlist URL
continuation_tokenNoPagination token returned by a previous request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does well: it enumerates the returned fields (title, URL, owning channel, video count, thumbnail, and per-video attributes) and explains the pagination mechanism. It doesn't mention read-only nature, auth, or rate limits, but as a fetch-by-id operation the key behaviors are disclosed.

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?

Three sentences, front-loaded with purpose, then return contents, then pagination. Little waste, though the middle sentence listing every returned field is dense and could be trimmed.

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?

With no annotations and no output schema, the description must (and largely does) convey the return structure and paging behavior an agent needs. It is complete enough to invoke correctly, missing only explicit read-only/auth context.

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 documents both parameters and the baseline is 3. The description adds only modest value by restating that `id` accepts an ID or URL and implying the `continuation_token` is for longer playlists; it adds no new syntax or format detail.

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 opens with a specific verb+resource ('Retrieve playlist metadata and items') and clarifies the accepted input forms ('by playlist id or full playlist URL'), which implicitly scopes it away from channel-level tools like youtube_channel_playlists. It never names an alternative sibling explicitly, so it falls short of the top score.

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: an agent infers it should call this when it already has a playlist id or URL. The one concrete instruction given is pagination ('Pass the returned continuation_token'), but there is no when/when-not guidance or named alternative such as youtube_channel_playlists for discovering playlists.

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