Skip to main content
Glama

channel_videos

List recent videos from a YouTube channel or playlist URL, with a configurable number, to support content research and monitoring.

Instructions

List recent videos of a channel or playlist URL (e.g. https://www.youtube.com/@name/videos).

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": {
      "url": "<url>"
    },
    "name": "channel_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about authentication needs, rate limits, pagination, ordering of results, or what 'recent' actually means in time or count terms. Only the input shape is conveyed, leaving the operation's behavior largely opaque.

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?

A single compact sentence with the resource and scope front-loaded, and the parenthetical example earns its place by clarifying accepted URL formats. No filler, though it is arguably too terse given the undocumented second parameter.

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?

The tool is simple (one required URL, one count) and an output schema exists, so return-format explanation is not needed. The main residual gap is the undefined 'n' parameter and the vague 'recent' qualifier, which keep it from being fully complete.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters. The example URL gives some meaning to the required 'url' parameter (channel handle or playlist form), but the 'n' parameter with its default of 10 is never mentioned in the description, so it must be inferred as a result-count limit. Coverage of parameter meaning is well short of what a 0%-covered schema requires.

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 uses the concrete verb 'List' with a specific resource, 'recent videos of a channel or playlist URL', and supplies an example URL that disambiguates the accepted input form. It is clear enough to distinguish from siblings like channel_stats or video_info, though it never explicitly names or contrasts those siblings.

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: an agent can infer this is the tool for enumerating a channel's videos, and the channel-vs-playlist mention hints at supported input variants. There is no explicit when-to-use / when-not-to-use guidance, and no routing toward channel_stats (metadata) or video_transcript (single-video content) alternatives.

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