Skip to main content
Glama
Sign In

YouTube Transcript + YouTube Search MCP

by com.getyoutubetranscript
OverviewDiscussionsAdmin

List Channel Playlists

list_channel_playlists
Read-only

Use this when the user wants to see the playlists a YouTube channel has published, for example a creator's course series or show seasons. Returns each playlist's id, title, link and video count, one page at a time. Pass a playlist's id to list_playlist_videos to see its videos. Pass continuation from a previous response for the next page.

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": "list_channel_playlists"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel @handle, URL, or UC... id. Required unless `continuation` is set.
continuationNoOpaque token from a previous response - fetches the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds real context beyond that: results are paginated one page at a time, a continuation token advances pages, and the returned fields are named (id, title, link, video count). It omits quota/rate-limit or failure behavior, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, each doing distinct work: trigger, return shape, pagination, and sibling hand-off. The trigger is front-loaded with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the returned fields and explaining pagination, and it documents both parameters' roles along with the next-step tool. An agent has everything needed to call this correctly and interpret the response.

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% and already explains both `channel` (handle/URL/UC id, required unless continuation) and `continuation`. The description's note about passing continuation for the next page restates the schema rather than adding format or edge-case detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('see the playlists a YouTube channel has published') and anchors it with concrete examples (course series, show seasons). It is clearly distinct from list_playlist_videos, which it explicitly hands off to.

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?

Gives a clear triggering condition ('when the user wants to see the playlists a channel has published') and names the follow-on tool for drilling into a playlist's videos. It does not state exclusions or contrast with search-type siblings, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YouTube Transcript + YouTube Search MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources