Skip to main content
Glama

YouTube: List Videos

youtube_list_videos
Read-only

List a channel's uploads, including private, unlisted, and scheduled videos, with status, duration, metrics, and URL; page through results and use youtube_get_video for full detail.

Instructions

This channel's uploads, newest first, including private, unlisted and scheduled ones: id, title, privacy, upload status, duration, views/likes/comments and URL. A video still processing shows upload_status uploaded; one that failed shows failure_reason or rejection_reason. A just-uploaded video can take a minute or more to appear here, because the uploads playlist is eventually consistent — youtube_get_video finds it at once. Costs 2 quota units per page (+1 the first time, to find the uploads playlist). For one video's full detail use youtube_get_video.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results per page (1-50, YouTube's own cap). Defaults to 25.
page_tokenNoThe `next_page_token` from the previous call, to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial behavior beyond that — quota cost (2 units per page, +1 first call to resolve the uploads playlist), eventual-consistency lag of a minute or more, and the meaning of upload_status/failure_reason/rejection_reason for processing and failed videos. That is exactly the context annotations cannot carry.

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?

Front-loaded with resource and returned fields, then failure-state semantics, then the consistency caveat, then cost, then the alternative. Every sentence carries distinct information; no restatement of the name or title.

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?

With no output schema, the description compensates by enumerating returned fields and explaining status values. Quota cost, pagination cost model, freshness behavior, and the sibling escape hatch are all covered for a simple two-parameter list tool.

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 coverage is 100% and both parameters (limit, page_token) are fully documented in the schema, so baseline 3 applies. The description only touches pagination indirectly via "per page" quota cost and adds no format or syntax detail beyond the 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?

Opens with a specific verb and resource plus scope and ordering: "This channel's uploads, newest first, including private, unlisted and scheduled ones", then enumerates the exact fields returned. An agent can distinguish it from youtube_get_video without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: "For one video's full detail use youtube_get_video", and implies the converse that this is the browsing/enumeration path. It also states the eventual-consistency caveat with the named workaround (youtube_get_video finds it at once), which is when-to-use guidance in practice.

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