Skip to main content
Glama

list_youtube_channel_videos

List all public videos from a YouTube channel using its uploads playlist. Supports pagination, filtering by shorts and live streams, and multiple order strategies.

Instructions

List videos for a channel (public data), with safe defaults.

Default behavior (safe + complete): - Uses the channel's uploads playlist (uploadsPlaylistId) to paginate through all uploaded videos.

Parameters: channel_ref: Same formats as resolve_youtube_channel. max_videos: Hard limit per tool call. The tool may return fewer items and set truncated=true. page_token: Token for pagination (from previous response nextPageToken). Alias: you may also pass next_page_token (some agents prefer it). include_shorts: Default false. If true, includes Shorts (best-effort classification). include_live: Default false. If true, includes live/upcoming videos (best-effort). parts_level: - basic (default): snippet + statistics + contentDetails - full: also requests status/liveStreamingDetails (heavier payload) order_strategy: - uploads_playlist (default): low quota, paginated. - local_sort: fetches a bounded subset then sorts locally. (Not paginated; page_token must be null.) - search_api: uses YouTube Search API ordering (expensive, capped). Explicit opt-in only. order_by: - date (default) - viewCount, likeCount, commentCount, duration Note: search_api supports only date and viewCount.

Returns (structured JSON): - items: video[] (YouTube API video resources) - nextPageToken: string | null - next_page_token: string | null (alias of nextPageToken for agent friendliness) - quotaEstimate: {estimatedUnits,strategy,notes[]} - truncated: bool - appliedMaxVideos: int - appliedOrder: {strategy, by}

Quota/performance notes: - Search API calls are expensive (quota ~100/unit per call) and may be capped for channels. - local_sort is bounded by max_videos and max_pages.

Safety notes: - Public data only; no private playlists/videos. - No file/network access except YouTube Data API endpoints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_byNodate
max_videosNo
page_tokenNo
channel_refYes
parts_levelNobasic
include_liveNo
include_shortsNo
order_strategyNouploads_playlist
next_page_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully bears the burden. It discloses public-only data, safe defaults, quota estimates, pagination, truncation, and safety notes (no file/network access). Behavior is transparent and complete.

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?

The description is well-structured with sections (default behavior, parameters, returns, notes). It is lengthy but every sentence adds value. Slightly verbose, but appropriate for complexity.

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?

Given 9 parameters, no annotations, and an output schema, the description is thorough. It covers all parameters, behavior, quotas, safety, and return structure. No gaps identified.

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?

Schema description coverage is 0%, but the description compensates by explaining each parameter in detail: channel_ref formats, max_videos as hard limit, page_token alias, include_shorts/live defaults, parts_level options, order_strategy/order_by options and constraints. It also explains return fields.

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 'List videos for a channel (public data), with safe defaults.' The name and title align perfectly. It differentiates from siblings like list_youtube_playlist_videos by focusing on channel videos.

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?

The description provides extensive usage guidance: default behavior, pagination, parameter explanations, and when to use different order strategies (e.g., 'Explicit opt-in only' for search_api). However, it does not explicitly contrast with sibling tools (e.g., when to use list_youtube_playlist_videos instead).

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/glonorce/youtube_mcp'

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