Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get channel overview

get_channel_info
Read-onlyIdempotent

Retrieve a YouTube channel’s name, description, subscriber and video counts, total views, and uploads playlist ID by channel ID or handle—or omit the channel for your own or the configured default.

Instructions

Channel name, description, subscriber count, video count, total views, and uploads playlist ID.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_channel_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoChannel ID (UC...) or handle (@name). Omit for your own channel (OAuth) or the configured default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds no behavior beyond that: nothing about auth requirements, whether OAuth is required for the default channel, quota/rate limits, or failure modes for unknown handles/channel IDs.

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?

It is short with no filler, but it is a sentence fragment leading with return fields rather than a purpose statement, so the most useful information is not front-loaded. Every word is about output, which the output schema already covers.

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

Completeness3/5

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

An output schema exists, so enumerating return fields is redundant rather than necessary, and for a single-param read tool the definition is minimally viable. Gaps remain around when to pick this over get_channel_analytics or compare_channels, and around auth expectations for the default channel.

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 single channel param already documents 'UC...' IDs versus '@name' handles plus the omit-for-default behavior. The description adds no parameter meaning of its own, which is acceptable given the schema does the work, but it means zero incremental value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text is a bare list of returned fields (name, description, subscriber count, video count, views, uploads playlist ID) with no verb, so the retrieval action must be inferred from the tool name. It conveys the resource but does nothing to distinguish it from siblings like get_channel_analytics, get_channel_report, or compare_channels.

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 when-to-use, when-not-to-use, or alternative-selection guidance appears anywhere in the description. The only usage-ish hint (omit the param for your own channel/default) lives in the input schema, not the description, so an agent gets no routing signal here.

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