Skip to main content
Glama
l4b4r4b4b4

YouTube MCP Server

by l4b4r4b4b4
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_channel_info

Retrieve YouTube channel metadata including title, description, subscriber count, video count, and total views.

Instructions

Get detailed information about a YouTube channel.

Retrieves channel metadata including title, description, statistics
(subscribers, videos, total views), and branding information.
Cached for 24 hours to minimize API quota usage.

Args:
    channel_id: YouTube channel ID (from search results, e.g., "UCuAXFkgsw1L7xaCfnd5JJOw")

Returns:
    Channel info dictionary with:
    - title, description, channel_id, url, thumbnail
    - subscriber_count, video_count, view_count
    - published_at

Example:
    >>> info = _get_channel_info("UCuAXFkgsw1L7xaCfnd5JJOw")
    >>> print(info["title"])
    "Vimjoyer"

Note:
    - Costs 1 quota unit per request (100x cheaper than search)
    - Cached for 24h in youtube.api namespace
    - Use after channel search to get full details

Caching Behavior:

  • Parameters that accept reference strings can accept a ref_id from a previous tool call

  • Large results return ref_id + preview; use get_cached_result to paginate

  • All responses include ref_id for future reference

Ref input compatibility: Support depends on the tool's input schema/validation. Some strictly typed parameters may reject string ref_ids before resolution.

Full retrieval: Use get_cached_result(ref_id, full=True) to get the complete value.

Preview Size: server default. Override per-call with get_cached_result(ref_id, max_size=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Discloses caching behavior (24 hours), quota cost (1 unit per request), and return structure. Without annotations, this adds important behavioral context. Could mention error handling for missing channels.

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

Conciseness3/5

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

The main description is well-structured with Args, Returns, Example, and Note. However, a large boilerplate section about general caching behavior is appended, which is not tool-specific and reduces conciseness, potentially confusing LLM agents.

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?

Given the presence of an output schema, the description covers purpose, usage timing, parameter details, caching, quota, and includes an example. It is complete and actionable for an LLM agent.

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?

With 0% schema coverage, the description fully compensates by explaining the parameter's source (from search results), giving a concrete example, and specifying its role. This exceeds baseline expectations.

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 gets detailed information about a YouTube channel, listing metadata fields and providing an example. It also suggests using after search, distinguishing it from sibling tools like search_channels.

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?

Explicitly says 'Use after channel search to get full details' and notes cost savings, providing clear context for when to use. Does not list when-not or alternatives explicitly, but the context is sufficient.

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/l4b4r4b4b4/yt-api-mcp'

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