Skip to main content
Glama
Sign In
YouTube Channel MCP

YouTube Channel MCP

by joinhackyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Channel outliers

find_outliers
Read-only

Rank a channel's videos by outlier score compared with neighboring uploads of the same format, showing over-performers to repeat and under-performers to fix or drop.

Instructions

Ranks the channel's videos by outlier score (views ÷ the median of neighbouring uploads of the same format). Shows what over-performed (repeat it) and what under-performed (fix packaging or drop the topic). Shorts and long videos are compared separately.

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": "find_outliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoall
channelNoWhich connected channel: channel ID (UC...), @handle or name. Omit to use the default channel.
max_videosNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully adds the scoring formula and the cohort rule (shorts and longs ranked separately), which is real behavioral context. It stops short of describing result size, pagination, or cost of the calculation, which matters for a ranked analytics query.

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?

Three short sentences, front-loaded with the definition, then the actionable interpretation, then the cohort caveat. No filler and no repetition of structured fields.

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?

For a read-only three-parameter analytics tool with no output schema, the description covers the metric, the ranking, and the cohort split, which is most of what an agent needs. The remaining gap is how the returned list is shaped and what 'neighbouring uploads' means operationally.

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 only 33%: channel is documented in the schema, but format and max_videos are not. The description partially compensates by explaining that shorts and long videos are compared separately, which clarifies the format enum's meaning, but max_videos (default 100, range 10-500) gets no explanation of what counts as a video in the ranked set.

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?

Names a specific verb (ranks) and resource (the channel's videos) and even defines the computed metric: views divided by the median of neighbouring uploads of the same format. That makes it clearly distinct from get_analytics or list_my_videos in substance, though it never names a sibling to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains what to do with the output ('repeat it', 'fix packaging or drop the topic'), which implies the decision context for using the tool, but gives no explicit when-to-use versus get_analytics or list_my_videos, and no exclusion or prerequisite guidance.

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

Deploy Server

Other Tools