Skip to main content
Glama

Youtube

by io.github.pipeworx-io

Yt Channel Videos

yt_channel_videos
Read-onlyIdempotent

List recent videos from a YouTube channel, ordered by date. Returns video ID, title, description, and publish date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesYouTube Data API v3 key from Google Cloud Console
channel_idYesChannel ID to list videos from
max_resultsNoNumber of videos to return (default 10, max 50)
published_afterNoFilter videos published after this ISO 8601 date
published_beforeNoFilter videos published before this ISO 8601 date

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
videosYesArray of video summary objects
total_resultsYesTotal number of videos in channel

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "total_results": {
+      "description": "Total number of videos in channel",
+      "type": "number"
+    },
+    "videos": {
+      "description": "Array of video summary objects",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Video description",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "ISO 8601 publish date",
+            "type": "string"
+          },
+          "thumbnail": {
+            "description": "Default thumbnail URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Video title",
+            "type": "string"
+          },
+          "video_id": {
+            "description": "Video ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "video_id",
+          "title",
+          "description",
+          "published_at",
+          "thumbnail"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "total_results",
+    "videos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-youtube-api-key",
+    "channel_id": "UCkRfArvrzheW2E7b6SVV7vA"
+  },
+  {
+    "_apiKey": "your-youtube-api-key",
+    "channel_id": "UCkRfArvrzheW2E7b6SVV7vA",
+    "max_results": 25,
+    "published_after": "2024-06-01T00:00:00Z"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. Description adds value by specifying ordering (by date) and return fields (ID, title, description, publish date). No contradictions.

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 sentences, front-loaded with action and return fields. Every word earns its place; no fluff.

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?

Description covers core functionality, but omits details like pagination, default max_results, or filtering semantics for date ranges. However, with annotations (openWorldHint) and output schema, it is mostly adequate.

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?

All 5 parameters are described in the input schema with 100% coverage. The description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states 'List recent videos from a YouTube channel, ordered by date' and lists return fields. This distinguishes it from sibling tools like yt_search (search by query) and yt_video_details (single video details).

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. With many sibling tools (yt_search, yt_video_details, yt_channel_details), the description should indicate scenarios like 'Use when you have a known channel ID and want a chronological list of recent videos' and when not to use it.

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

All Youtube toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The five yt_* tools are distinct, but the majority of the set is dominated by overlapping Pipeworx tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical entry points, and the multiple polymarket_* tools cover closely related edge/arbitrage/fill-risk territory. An agent could easily select the wrong one.

Naming Consistency3/5

Most names use lowercase snake_case, but conventions are mixed: yt_* and polymarket_* are prefix-scoped, pipeworx_* mixes verb-first and noun-first names, and there are standalone verbs like remember, recall, and forget. The server is named Youtube, yet the bulk of tools follow unrelated Pipeworx/Polymarket naming.

Tool Count2/5

36 tools is heavy for a server named Youtube, and only 5 actually address YouTube functionality. The remaining 31 tools cover unrelated data-research and prediction-market features, making the surface bloated and off-purpose.

Completeness3/5

The YouTube subset covers search, channel info, channel videos, video details, and comments, which handles basic read-only queries. Missing playlists, captions/transcripts, and subscription/upload actions leave notable gaps for a YouTube-focused server.

Resources