Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Compare channels

compare_channels
Read-onlyIdempotent

Benchmark up to 10 YouTube channels side by side by comparing subscribers, views, engagement, upload frequency, Shorts share, and top recent videos for competitor tracking.

Instructions

Benchmark channels side by side: subscribers, total views, and over their recent uploads the median views, engagement rate, upload frequency, share of Shorts and top video.

Public data; about 3 quota units per channel. Good for competitor tracking.

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": {
      "channels": "<channels>"
    },
    "name": "compare_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsYes1-10 channel IDs (UC...) or @handles; 'mine' for your own channel (OAuth).
recent_videosNoLatest uploads to sample per channel, 1-50.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description does add two things annotations cannot express: that the data is public and that each channel costs roughly 3 quota units, which is valuable cost-planning context. It stops there, saying nothing about rate limits, failure modes for invalid handles, or partial results when a channel is private.

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?

Two tightly packed sentences: metrics first, then cost and data source, then the recommended use case. Every clause carries information and nothing is padded or repeated from the schema.

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?

With an output schema present, return-value detail is not required, and the description covers data provenance, cost and intended use. The only gap is operational edge cases, such as what happens with invalid handles or private channels in a batch of up to 10.

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%, so both parameters are already documented, including the 1-10 range and the 'mine' OAuth case. The phrase 'over their recent uploads' loosely ties to the recent_videos sampling parameter but adds no format or behavioral detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 opens with a specific verb and resource ('Benchmark channels side by side') and enumerates the exact metrics returned: subscribers, total views, median views, engagement rate, upload frequency, Shorts share and top video. The multi-channel comparison framing implicitly separates it from single-channel analytics tools, though it never names a sibling to route against.

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?

'Good for competitor tracking' gives a concrete use case and 'Public data' signals it works without OAuth for channels other than your own, which is real routing context. There is no explicit when-not guidance or named alternative for single-channel deep-dives, so it stops short of full alternative coverage.

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