Skip to main content
Glama

YouTube channel details

youtube_channel
Read-onlyIdempotent

Get a public YouTube channel: name, handle, description, subscriber count, video count, total views, join date, country, the links on its About page, keywords, avatar, banner and verified badge. For its uploads, call youtube_channel_videos.

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": "<channel>"
    },
    "name": "youtube_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesA YouTube channel: an @handle (@NASA), a channel link (https://www.youtube.com/@NASA, /channel/UC…, /c/…, /user/…) or a channel id (UCLA_DiR1FfKNvjuUpBHmylQ).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. With no output schema, the description carries the return-shape burden and does so by enumerating the exact fields returned, and the word 'public' usefully signals that only publicly visible channels resolve. It stops short of stating failure behavior for unresolvable handles or link formats.

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, zero filler, with the returned-field inventory front-loaded and the sibling routing placed last where it belongs. Every clause conveys information an agent would otherwise have to infer.

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?

For a single-parameter read tool with no output schema, the description supplies the essential missing piece — the field inventory — plus the sibling boundary, which is enough to call it correctly. Minor residual gaps (invalid-input behavior, whether the call is rate-limited) are low-stakes for a read-only public lookup.

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% and the schema already spells out every accepted identifier form (@handle, /channel/, /c/, /user/ links, raw channel id) with length bounds. The description adds no input meaning beyond that — the word 'handle' appears only in the list of returned fields, not as input guidance — so this sits at the schema-driven baseline.

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?

States a specific verb and resource ('Get a public YouTube channel') and then enumerates the exact fields returned — name, handle, subscriber count, video count, join date, links, keywords, avatar, banner, verified badge — which makes the scope unambiguous. It also explicitly names the boundary against the sibling tool for uploads, so an agent can distinguish it from youtube_channel_videos without opening either schema.

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 final sentence gives explicit routing: 'For its uploads, call youtube_channel_videos,' which is a real when-to-use-elsewhere rule rather than implied usage. What it doesn't cover is the other common case — locating a channel when you only have a display name or search query (youtube_search) — and it gives no exclusions about private or non-existent channels.

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.

Resources