Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

List a channel's videos

list_channel_videos
Read-onlyIdempotent

Retrieve a channel's uploaded videos newest first with basic stats, including views, likes, comments and duration, and paginate results using a next page token.

Instructions

A channel's uploaded videos, newest first, with basic stats. Paginated via next_page_token.

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_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel ID (UC...) or handle (@name). Omit for your own channel (OAuth) or the configured default.
page_tokenNonext_page_token from a previous call, for the next page.
max_resultsNoItems per page, 1-50.
include_statsNoInclude views, likes, comments and duration.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is low. The description adds useful context beyond them — newest-first ordering and next_page_token pagination — but says nothing about quota cost, visibility limits (public vs. private uploads), or what happens when a channel has no uploads.

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?

Two short sentences with the resource and ordering front-loaded and pagination appended. No filler, no restatement of the title.

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 low-complexity list tool with full schema coverage, complete annotations, and an output schema covering return values, the description is nearly sufficient. It only falls short on the visibility/scope question and on routing relative to the many sibling listing tools.

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 all four parameters (channel, page_token, max_results, include_stats) are already well documented. The description's 'Paginated via next_page_token' merely echoes the page_token schema text and adds no new meaning about parameter interaction or defaults.

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 names a specific resource and scope ('A channel's uploaded videos') plus two behaviors the name alone doesn't convey: newest-first ordering and basic stats. It doesn't name any sibling, so an agent can't tell from the text alone how this differs from search_videos or get_top_videos.

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?

There is no when-to-use or when-not-to-use guidance; the only conditional is the schema-level 'Omit for your own channel'. With siblings like search_videos, get_top_videos, and get_playlist_items in scope, an agent is left to infer that this is the plain chronological upload listing.

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