mcp-youtube

getChannelStatistics

Read-onlyIdempotent

Retrieve subscriber count, view count, video count, and channel creation date for multiple YouTube channels to analyze performance and reach.

Instructions

Retrieves statistics for multiple channels. Returns detailed metrics including subscriber count, view count, video count, and channel creation date for each channel. Use this when you need to analyze the performance and reach of 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": "getChannelStatistics"
  }
}

Input Schema

Name	Required	Description	Default
`channelIds`	Yes	Array of YouTube channel IDs to get statistics for

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.5May 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.0Sep 11, 2025

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe read-only behavior. The description adds value by specifying the returned metrics (subscriber count, view count, etc.), which helps the agent understand the output. No additional behavioral traits (e.g., rate limits) are disclosed, but the annotations cover the safety profile.

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?

The description is extremely concise, consisting of two sentences that front-load the action and purpose. Every word earns its place, with no redundancy or unnecessary details.

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?

Given the tool's simplicity (one parameter, full schema coverage, annotations), the description is fairly complete. It explains the return metrics and the use case. It could optionally mention limitations like maximum array size, but that is not critical for a basic stats retrieval tool.

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?

The input schema has 100% coverage with a detailed description for the only parameter channelIds. The description adds no new semantic information beyond what the schema provides, so the baseline of 3 is appropriate.

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 the tool retrieves statistics for multiple channels and lists specific metrics. The verb 'retrieves' and resource 'statistics for multiple channels' are specific. It distinguishes from sibling tools like getChannelTopVideos and getVideoDetails by focusing on batch channel statistics.

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 provides explicit usage context: 'Use this when you need to analyze the performance and reach of multiple YouTube channels.' It does not mention when not to use or provide alternatives, but the guidance is clear and actionable.

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

Deploy Server