YouTube MCP Server

channels_getChannels

Retrieve details for multiple YouTube channels using channel IDs. Optionally include enrichment fields like latest upload date.

Instructions

Get information about multiple YouTube channels

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": {
      "channelIds": "<channelIds>"
    },
    "name": "channels_getChannels"
  }
}

Input Schema

Name	Required	Description
`parts`	No	Parts of the channel resource to retrieve
`channelIds`	Yes	A list of YouTube channel IDs
`includeLatestUpload`	No	Whether to include the latestVideoPublishedAt enrichment field

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic operation, omitting authentication needs, rate limits, return value structure, or any side effects. This is insufficient for an agent to use safely.

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 description is a single concise sentence, but it sacrifices completeness. It is front-loaded and to the point, but could afford a few more sentences to improve clarity without becoming verbose.

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

Completeness2/5

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

Given the tool has 3 parameters, no output schema, and no annotations, the description should provide more context about return values, usage limits, or parameter constraints. It is currently too brief to be fully helpful.

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 coverage is 100%, so baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides. No extra context on parts, channel IDs format, or includeLatestUpload implications.

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

Purpose4/5

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

The description clearly states it retrieves information for multiple YouTube channels, distinguishing it from the sibling tool channels_getChannel which handles a single channel. However, it could be more specific about what 'information' encompasses.

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 guidance is provided on when to use this tool versus alternatives like channels_getChannel for single channels or channels_searchChannels for discovery. The agent receives no contextual help for tool selection.

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

Deploy Server