Skip to main content
Glama

get_channel_rss_videos

Retrieve recent YouTube channel uploads from the Atom RSS feed without API quota or a key, returning up to 15 videos for monitoring channel activity.

Instructions

Latest uploads from the Atom feed — port of youtube-mcp get_channel_rss_videos.

Layer 4 (RSS). Quota: 0 units, no key. Feed exposes at most 15 entries.

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_id": "<channel_id>"
    },
    "name": "get_channel_rss_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYes
max_resultsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses zero quota cost, no API key requirement, and a hard 15-entry ceiling on the feed. It stops short of stating failure behavior for an invalid channel_id, ordering guarantees, or whether any result is cached, which matters for a tool with no readOnlyHint or other safety signals.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded with the core purpose. But "port of youtube-mcp ``get_channel_rss_videos``" is internal provenance noise for an agent, and "Layer 4 (RSS)" is cryptic shorthand that consumes space without informing.

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?

An output schema exists, so return-shape explanation is rightly omitted, and the 15-entry cap plus quota profile cover the main operational facts. The missing piece is channel_id semantics, which neither the description nor the schema supplies, leaving the required parameter under-specified relative to the tool's simplicity.

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 0%, so the description must carry the parameter burden. It partly does: "Feed exposes at most 15 entries" explains why max_results defaults to 15 and that higher values are futile. The required channel_id is left completely unexplained — no format, prefix, or handle-vs-ID guidance — which is a meaningful gap for the only required parameter.

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?

"Latest uploads from the Atom feed" names a concrete resource and retrieval mechanism, so an agent knows it returns a channel's recent videos without opening the schema. It does not name a sibling (e.g. youtube_get_channel_videos) to contrast the RSS path against the API path, so differentiation is only implied by "Layer 4 (RSS)".

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?

"Quota: 0 units, no key" implies this is the cheap/free path an agent should prefer when quota is a concern, which is real usage guidance. However, it never states when to prefer youtube_get_channel_videos or search_videos instead, and "Layer 4" is opaque without the surrounding system's tier documentation.

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