Skip to main content
Glama

YouTube channel's videos, Shorts or live streams

youtube_channel_videos
Read-onlyIdempotent

List a YouTube channel's uploads from its Videos, Shorts or Live tab, newest first, most popular first or oldest first, about 30 per page, each with title, views, length, age and thumbnail. A channel without that tab returns an empty page. First page: give channel (and tab, sort). Next pages: give only cursor until next_cursor is null.

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

Input Schema

NameRequiredDescriptionDefault
tabNoThe channel's Videos, Shorts or Live tab.videos
sortNoNewest first, most popular first, or oldest first.newest
cursorNoThe next_cursor of the previous answer, exactly as returned, for the next page. Leave it out for the first page; with it, nothing else is needed.
channelNoA YouTube channel: an @handle (@NASA), a channel link (https://www.youtube.com/@NASA, /channel/UC…, /c/…, /user/…) or a channel id (UCLA_DiR1FfKNvjuUpBHmylQ).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description earns credit for what it adds: ordering options, 'about 30 per page', the per-item fields returned (title, views, length, age, thumbnail), and the edge case that a missing tab yields an empty page. It does not mention auth or rate-limit behavior, which is the main remaining gap.

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?

Three sentences, front-loaded with purpose, then ordering and page shape, then the call pattern. Every clause carries operational information and nothing is redundant.

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 four optional parameters and no output schema, the description does the necessary work of describing returned fields and page size. The only thing an agent might still wonder about, cursor expiry or total page counts, is arguably outside scope, so the definition is essentially complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the pagination contract ('with it, nothing else is needed') and that tab and sort only apply on the first page. The channel-input forms are already enumerated in the schema, so that portion is repetition rather than added meaning.

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 and resource: 'List a YouTube channel's uploads from its Videos, Shorts or Live tab.' That is enough to distinguish it from youtube_channel (channel metadata) and youtube_search (query-based discovery), but it never names those siblings or states the boundary explicitly, so it lands just short of a 5.

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?

Invocation guidance is unusually explicit for pagination: 'First page: give channel (and tab, sort). Next pages: give only cursor until next_cursor is null.' That tells the agent exactly what to pass on each call. It gives no when-to-use-vs-alternative guidance (e.g., when to prefer youtube_search), so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources