Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

Get Channel

youtube_get_channel
Read-onlyIdempotent

Retrieve public channel details including title, description, subscriber count, and video count by providing a channel ID, @handle, or legacy username.

Instructions

Retrieve public details for any YouTube channel by one of three identifiers: channel ID, @handle, or legacy username. Exactly one of channelId, handle, or username must be supplied.

Args:

  • channelId (optional): The channel's unique ID, e.g. "UCxxxxxxxx".

  • handle (optional): The channel's @handle. The leading @ is stripped automatically, e.g. "@MrBeast" or "MrBeast".

  • username (optional): A legacy YouTube username (deprecated by YouTube but still supported), e.g. "PewDiePie".

  • response_format (optional): "markdown" (default) or "json".

Returns (JSON shape):

{
  "id": "UCxxxxxxxx",
  "snippet": { "title", "description", "customUrl", "publishedAt", "country", "thumbnails" },
  "statistics": { "subscriberCount", "videoCount", "viewCount", "commentCount" },
  "brandingSettings": { "channel": { "title", "description", "keywords" } },
  "contentDetails": { "relatedPlaylists": { "uploads" } }
}

Examples:

  • "Look up channel UCxxxxxxxx" → pass channelId: "UCxxxxxxxx".

  • "Get info on @MrBeast" → pass handle: "@MrBeast".

  • "Find channel for username PewDiePie" → pass username: "PewDiePie".

Errors:

  • 400: none of the three identifiers was provided.

  • 404: channel not found or not publicly accessible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdNoYouTube channel ID, e.g. UCxxxxxxxx. Provide exactly one of channelId, handle, or username.
handleNoChannel @handle, e.g. "@MrBeast" or "MrBeast". The leading @ is stripped automatically.
usernameNoLegacy YouTube username (deprecated). Provide exactly one of channelId, handle, or username.
response_formatNoOutput format: "markdown" (default) for a human-readable summary, "json" for the raw API object.markdown
Behavior4/5

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

Annotations already indicate idempotent, read-only, non-destructive behavior. The description adds that it retrieves only public details and accepts three identifier types, with automatic @-stripping, providing behavioral context beyond annotations.

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

Conciseness4/5

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

The description is structured into clear sections (Args, Returns, Examples, Errors) and is comprehensive without being overly verbose. Some redundancy exists but overall it's efficient.

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?

Combined with the schema and annotations, the description provides thorough context: return shape, error handling, examples, and identifier usage. It is fully complete for a read-only lookup tool with no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are well-documented in the schema, and the description adds examples, error scenarios, and clarifies the relationship between the three optional identifiers, significantly enhancing understanding.

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 it retrieves public details for a YouTube channel by three specific identifiers, distinguishing it from sibling tools like youtube_get_my_channel.

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 specifies exactly when to use the tool (retrieve channel by ID/handle/username) and provides error conditions. It could explicitly contrast with similar tools like youtube_channel_summary, but overall it provides clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server