Skip to main content
Glama

YouTube channel

run_youtube_channel
Read-onlyIdempotent

Get the videos, shorts and streams of a YouTube channel or playlist (or a single video by URL): title, description, views, likes, comments, duration, hashtags, subtitles and the channel's subscribers, total videos and views. 5 points per returned record.

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

Input Schema

NameRequiredDescriptionDefault
urlYesChannel (@handle or URL), playlist or video URL. e.g. @NASA
max_resultsNoVideos (up to 1000) Default: 10.
sort_videos_byNoSort channel videos by. Options: POPULAR = Popular, OLDEST = Oldest
subtitles_formatNoSubtitle format. Options: vtt = WEBVTT, xml = XML, plaintext = Plain text
download_subtitlesNoDownload subtitles (when present on the video)
max_results_shortsNoShorts (up to 1000) Default: 0.
subtitles_languageNoSubtitle language. Options: any = Any, de = German, es = Spanish, fr = French, it = Italian, ja = Japanese, ko = Korean, nl = Dutch, pt = Portuguese, ru = Russian
max_results_streamsNoStreams (up to 1000) Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. The description adds genuinely non-derivable information: pricing at '5 points per returned record', which signals a metered, cost-scaling read and implies result-count control matters. It stops short of covering pagination, rate limits, or that shorts/streams default to zero records.

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 sentence that front-loads the resource and scope, then the returned fields, then the cost note. No filler and no repetition of schema detail.

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 no output schema, the field enumeration serves as an effective return-value preview, and the per-record cost note tells the agent how to size max_results. Missing only a hint that shorts/streams are opt-in (default 0) and that subtitles require download_subtitles.

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%, so every parameter including enums and defaults is already documented. The description clarifies that the url argument accepts a channel, playlist or video URL, but that duplicates the schema; it adds nothing about max_results vs max_results_shorts/streams or the sort/subtitle options.

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 states a specific verb and resource — retrieve videos, shorts and streams from a YouTube channel or playlist, or a single video by URL — and enumerates the returned fields (title, views, likes, subscribers, etc.). It implicitly separates itself from run_youtube_search (which takes a query) by framing the input as a channel/playlist/video URL, but never names a sibling explicitly.

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 implied by the input shape: use this when you have a channel handle, playlist or video URL. There is no explicit when-not guidance and no reference to run_youtube_search, run_youtube_shorts or run_youtube_comments, so the agent must infer the routing from sibling names alone.

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.