Skip to main content
Glama

list_channel_videos

Enumerate a YouTube channel's uploads without downloading video bytes, excluding Shorts under 60 seconds, with configurable limit and oldest-first or newest-first sorting.

Instructions

Enumerate video uploads from a channel without downloading bytes. Excludes Shorts (<60s). Defaults to chronological oldest-to-newest order.

Args: channel_url: YouTube channel uploads URL (e.g. 'https://www.youtube.com/@channel/videos'). limit: Maximum number of videos to list (default: 30). sort_order: 'oldest_first' (recommended for research) or 'newest_first'.

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": {
      "channel_url": "<channel_url>"
    },
    "name": "list_channel_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sort_orderNooldest_first
channel_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that bytes are not downloaded and that Shorts under 60s are excluded, which are real behavioral traits. It says nothing about pagination, invalid-channel handling, rate limits, or whether the listing is a snapshot, which matters for a scraping-style tool.

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 front-loaded sentences establish purpose, exclusion, and default ordering before the Args block. Every sentence carries information and nothing is padded.

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?

An output schema exists, so return-value shape needn't be explained, and the parameter block covers all three inputs for a simple read tool. Only edge-case behavior (maximum limit, malformed URLs, pagination) is left unaddressed.

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 0%, and the Args block compensates well: channel_url gets a concrete format example, limit gets a default, and sort_order gets both valid values plus a recommendation. It omits any cap on limit and does not clarify whether other URL forms (e.g. /shorts or /playlists) are accepted.

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, 'Enumerate video uploads from a channel', and immediately scopes it with 'without downloading bytes' and the Shorts exclusion. That functionally separates it from transcribe_youtube, but no sibling is named explicitly, so it falls 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 Guidelines3/5

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

Usage is only implied: 'oldest_first' (recommended for research) hints at the intended context and the default is stated. There is no explicit statement of when to choose this over get_video_info or transcribe_youtube, and no when-not-to-use guidance.

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