Skip to main content
Glama

Channel Stats

tubegrade_get_channel
Read-onlyIdempotent

Stats for one YouTube channel: subscribers, total views and videos, average views per recent upload, upload frequency, average video length, country and description. When TubeGrade has tracked the channel, the response also includes a growth block with subscriber, view and video counts over recent months; gained is the change per period, and where readings are several periods apart it is the per- period average.

Use when the user asks how big a channel is, how it is growing, or what its typical video gets. Accepts a channel id (UC…), an @handle, or a channel URL. Public data only: no private YouTube Analytics (watch time, retention, CTR, traffic sources, revenue).

Cost: 5 credits per call.

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": {
      "channel_id": "<channel_id>"
    },
    "name": "tubegrade_get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel id (e.g. 'UCX6OQ3DkcsbYNE6H8uQQuVA'), an @handle (e.g. '@MrBeast'), or a channel URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (readOnly, idempotent, openWorld): it discloses the credit cost (5 per call), the public-data-only constraint excluding YouTube Analytics metrics, and the conditional presence and semantics of the `growth`/`gained` block (per-period change averaged over sparse readings). These are meaningful behaviors not captured by structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the return contents, then conditional behavior, then usage and cost. Dense but every clause carries information; the growth-block sentence is slightly involved but justified for interpreting results.

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

Completeness5/5

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

An output schema exists, yet the description still clarifies the otherwise ambiguous `growth`/`gained` semantics and adds cost and data-scope context. For a read-only single-param stat tool, nothing needed to invoke it correctly is missing.

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% and there is a single parameter, so the schema already documents accepted formats. The description echoes the id/@handle/URL forms without adding new syntax or constraints, so the baseline of 3 applies.

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?

Specific verb+resource ('Stats for one YouTube channel') with an enumerated return set (subscribers, views, videos, avg views, upload frequency, length, country, description). It is clearly distinguishable from siblings like tubegrade_channel_videos or tubegrade_channel_transcripts, which fetch content rather than aggregate stats.

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?

Explicit when-to-use ('Use when the user asks how big a channel is, how it is growing, or what its typical video gets') and a clear boundary exclusion ('Public data only: no private YouTube Analytics'). No sibling alternative is named for adjacent needs, so it falls short of a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources