Skip to main content
Glama

Youtube

by io.github.pipeworx-io

Yt Channel Details

yt_channel_details
Read-onlyIdempotent

Get YouTube channel information and statistics including subscriber count, video count, view count, description, and custom URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesYouTube Data API v3 key from Google Cloud Console
usernameNoChannel username (alternative to channel_id)
channel_idNoChannel ID (starts with UC...)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsYesArray of channel detail objects

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": {
+    "channels": {
+      "description": "Array of channel detail objects",
+      "items": {
+        "properties": {
+          "country": {
+            "description": "Country code if available",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "custom_url": {
+            "description": "Custom channel URL if available",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Channel description",
+            "type": "string"
+          },
+          "id": {
+            "description": "Channel ID",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "ISO 8601 channel creation date",
+            "type": "string"
+          },
+          "subscriber_count": {
+            "description": "Subscriber count (null if hidden)",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "thumbnail": {
+            "description": "Channel thumbnail URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Channel title",
+            "type": "string"
+          },
+          "uploads_playlist": {
+            "description": "Playlist ID containing all uploads",
+            "type": "string"
+          },
+          "video_count": {
+            "description": "Total video count",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "view_count": {
+            "description": "Total channel view count",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "description",
+          "custom_url",
+          "published_at",
+          "country",
+          "thumbnail",
+          "view_count",
+          "subscriber_count",
+          "video_count",
+          "uploads_playlist"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "channels"
+  ],
+  "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",
+    "username": "LinusTechTips"
+  }
+]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnly, idempotent, not destructive. The description adds value by specifying the type of data returned (subscriber count, etc.), but does not disclose potential rate limits or API key requirements beyond the schema.

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?

Single sentence, 14 words, front-loaded with the essential action. No redundant information.

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?

Given low complexity, full schema coverage, and annotations, the description is mostly complete. However, it lacks clarification on parameter relationships (e.g., when to use channel_id vs username).

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 coverage is 100%, with all three parameters fully described. The description adds no additional parameter-specific details beyond listing them in the purpose.

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?

The description uses a specific verb 'Get' and resource 'YouTube channel information and statistics', listing concrete data points. It clearly distinguishes from sibling tools like yt_channel_videos and yt_search.

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 guidance on when to use this tool versus alternatives. The sibling list includes many YouTube-related tools, but the description provides no selection criteria or context.

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