Skip to main content
Glama

channel_stats

Analyze a YouTube channel's recent videos to calculate average and median views, identify high-view videos, and determine typical length and upload cadence.

Instructions

Quick channel analysis over its latest n videos (max 50): average/median views, best videos, typical length and upload cadence. url like https://www.youtube.com/@name/videos

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": {
      "url": "<url>"
    },
    "name": "channel_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that analysis is limited to the latest n videos with a maximum of 50 and lists the computed statistics, which implies a read-only aggregation. It does not explicitly state read-only behavior, permissions, rate limits, or handling of private/deleted videos, so material gaps remain.

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 definition is a compact, front-loaded sentence that states the operation, scope, and output metrics, followed by a concrete URL example. Every phrase contributes useful information and there is no redundant wording.

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 simple two-parameter aggregation tool with an output schema available, the description covers the essential scope, the n limit, the metrics produced, and the URL format. The main missing element is explicit routing versus sibling channel and video tools, but the core invocation requirements are adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: n is defined as the number of latest videos with a maximum of 50, and url is illustrated with a concrete channel URL format. It omits the default value of 30, but otherwise adds meaningful semantics beyond the bare schema.

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 states a specific verb and resource: channel analysis over the latest n videos, with named metrics such as average/median views, best videos, typical length, and upload cadence. It is clearly distinguishable from transcript or video-level siblings, though it does not explicitly name the closest alternative, channel_videos.

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?

The phrase "Quick channel analysis" implies a summary use case, and "latest n videos (max 50)" scopes when the tool is appropriate. However, it gives no explicit when-not guidance and does not route the agent to alternatives such as channel_videos or video_info for broader or video-level needs.

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