Skip to main content
Glama
Diterex

youtube-research-mcp

by Diterex

list_channel_videos

Read-onlyIdempotent

List a YouTube channel's uploads, newest first, without an API key. Survey content to pick videos for transcription; also accepts playlist URLs.

Instructions

List a YouTube channel's uploads, newest first, without an API key.

Use this to survey what a channel has published before deciding which videos are worth transcribing. Also accepts playlist URLs.

Args: channel_url: A handle ('@mwganson'), a bare name ('mwganson'), a channel ID ('UCxxxx...'), any youtube.com channel URL (with or without a /videos, /shorts or /streams tab), or a playlist URL. max_results: How many videos to return, newest first (1-1000, default 50). resolve_all_dates: False (default) fills upload dates for roughly the 15 most recent videos from the channel's RSS feed, which is one extra cheap request. True fetches every listed video's metadata to date the whole list - accurate but roughly one request per video, so only use it on small max_results.

Returns: { "channel": str | None, # display name "channel_id": str | None, # UC... id "channel_url": str, # URL actually listed "total_videos": int | None, # total on the channel/playlist, if known "count": int, # videos in this response "videos": [ { "video_id": str, # e.g. "Tbiu_rMJolk" "title": str, "url": str, # watch URL, feed straight to get_video_transcript "duration_seconds": int | None, "duration": str | None, # "44:19" "view_count": int | None, "upload_date": str | None # "2022-08-14", None if not resolved } ] }

Errors: Raises ValueError for an unparseable channel reference and RuntimeError with an actionable message if YouTube refuses the listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_urlYes
max_resultsNo
resolve_all_datesNo
Behavior4/5

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

Annotations already convey read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds valuable context beyond annotations: the cheap RSS feed vs. full video metadata trade-off for resolve_all_dates, the fact it works without an API key, and error types (ValueError, RuntimeError). This is meaningful but does not cover rate limits or network behavior details.

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?

The description is structured with Intro, Args, Returns, and Errors sections. Each section is dense but not redundant. Front-loaded with the core purpose and use case. The length is justified by the tool's complexity and the absence of an output schema.

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?

The description fully covers the tool's behavior, parameters, return value structure, and error conditions. Since there is no output schema, the detailed Returns block is essential and well done. Combined with the usage guidance, the agent has complete context to decide and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero descriptions (coverage 0%), so the description must fully compensate. The Args section explains each parameter with detailed semantics: channel_url accepts handles, bare names, IDs, URLs, and playlist URLs; max_results range and default; resolve_all_dates behavioral trade-offs. This goes far beyond the bare schema.

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?

The description clearly states the tool lists a YouTube channel's uploads, newest first, without an API key, and explicitly frames it as a survey step before deciding which videos to transcribe. This specific verb+resource+scope distinguishes it from siblings like get_video_transcript or search_youtube.

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?

It provides a clear use case ('Use this to survey what a channel has published before deciding which videos are worth transcribing') and mentions playlist URL support, but it does not explicitly state when not to use this tool or name alternative tools for different tasks. No exclusions are given, so it earns a 4 rather than a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Diterex/youtube-research-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server