Vee3

youtube.channel_details

Fetch metadata for a public YouTube channel by channel id or URL.

Accepts a channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg) or common YouTube channel URLs (for example https://www.youtube.com/@WWE). Returns title, username, description, subscriber and view counts, join date, verification flags, avatar and banner images, keywords, and external links.

Cost = 10 tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`channel_id`	Yes	YouTube channel id or URL (for example UCJ5v_MCY6GNUBTO8-D3XoAg or https://www.youtube.com/@WWE).

Output Schema

TableJSON Schema

Name	Required	Description
`links`	No	External links listed on the channel About page.
`stats`	No	Public channel statistics.
`title`	No	Channel display name.
`avatar`	No	Channel avatar images at different sizes.
`badges`	No	Channel badges (for example Official Artist Channel).
`banner`	No	Channel banner images for desktop, mobile, and TV layouts.
`country`	No	Country associated with the channel when available.
`keywords`	No	Channel keywords from the About page.
`username`	No	Public @ handle when available.
`artistBio`	No	Artist bio text when the channel is a music artist.
`channelId`	No	Canonical YouTube channel id.
`isVerified`	No	Whether the channel is verified.
`joinedDate`	No	Channel creation date (ISO 8601).
`description`	No	Channel About description.
`isFamilySafe`	No	Whether the channel is marked family safe.
`joinedDateText`	No	Human-readable join date.
`canonicalBaseUrl`	No	Canonical channel path on YouTube when available.
`hasBusinessEmail`	No	Whether a business email is available for contact.
`isVerifiedArtist`	No	Whether the channel is a verified artist channel.

Schema Changelog

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

Changed2 schema fields changedJun 21, 2026

removedOutput schema / $defs / YoutubeChannelDetailsResponseKeywordsItem

Removed value: -{
-  "additionalProperties": true,
-  "properties": {
-    "keyword": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "description": "Single keyword string.",
-      "title": "Keyword"
-    }
-  },
-  "title": "YoutubeChannelDetailsResponseKeywordsItem",
-  "type": "object"
-}

changedOutput schema / properties / keywords / anyOf

Previous value: -[
-  {
-    "items": {
-      "$ref": "#/$defs/YoutubeChannelDetailsResponseKeywordsItem"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description discloses that it only works for public channels, lists the specific metadata returned, notes the token cost, and gives accepted input formats, which is valuable given no annotations are present.

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?

The description is three sentences, front-loaded with the core purpose, includes concrete examples and output fields, and is free of fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter tool with an output schema, the description covers input formats, output fields, public-channel constraint, and cost, making it fully contextual.

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?

The schema description covers the channel_id parameter fully with examples, and the description repeats this information, so the description adds no new parameter semantics beyond the schema.

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 clearly states 'Fetch metadata for a public YouTube channel by channel id or URL' with a specific verb and resource, and lists the returned metadata fields, distinguishing it from sibling tools like youtube.channel_search or youtube.channel_videos.

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

Usage Guidelines4/5

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

The description provides clear context on how to invoke the tool (by channel id or URL) and implies its use case (fetching channel metadata), but it does not explicitly mention alternatives or when not to use it, though this is not necessary given the clarity.

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

All Vee3 tools Inspect

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.