Skip to main content
Glama

youtube_list_channel_videos

Read-only

List recent video uploads and their statistics for any public YouTube channel. Provide the channel ID or @handle to retrieve data about recent content performance.

Instructions

List recent uploads with statistics for ANY public channel, by channel ID or @handle (about 3 quota units per page).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channelId": "<channelId>"
    },
    "name": "youtube_list_channel_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesA channel ID (UC...) or an @handle.
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
  2. Addedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds a genuinely useful cost signal (~3 quota units per page) plus an implicit ordering signal ('recent'). It does not disclose pagination behavior (though pageToken exists in schema), what 'with statistics' actually returns, or what happens for private/nonexistent channels.

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?

A single front-loaded sentence that delivers purpose, scope, input forms and cost with no filler. Nothing could be cut without losing information.

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

Completeness3/5

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

For a three-parameter read tool with full schema coverage and readOnlyHint, the description covers purpose and cost, but leaves real gaps: 'statistics' is never defined, result ordering is only implied by 'recent', and with no output schema there is nothing else to tell the agent what comes back.

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%, with each of channelId, pageToken and maxResults documented, so the baseline is 3. The description restates the channelId duality (ID or @handle) and the 'per page' framing hints at pagination, but adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource: list recent uploads with statistics for a channel, and clarifies that this works for ANY public channel, which implicitly separates it from the owned-video tools in the sibling list. It stops short of naming the sibling it supersedes or clarifying how it differs from youtube_get_channel, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope qualifier 'ANY public channel' implies when this tool applies (other channels, not just your own), and 'by channel ID or @handle' tells the agent what inputs are accepted. However, there is no explicit when-to-use, no when-not-to-use, and no named alternative such as youtube_list_owned_videos for the caller's own uploads.

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

Deploy Server

Other Tools