SiteCheck Shop & Social

Social Blade creator statistics for a YouTube, Instagram

social_socialblade

Read-only

Social Blade creator statistics for a YouTube, Instagram, TikTok or Twitch account: followers/subscribers, views or likes, uploads, engagement rate and averages where Social Blade has them, Social Blade grade and ranks, country and category, plus the daily history Social Blade shows publicly (about 15 days). From socialblade.com's public profile pages through a residential proxy. Related tools on this server, for a different need: social_instagram when you need engagement snapshot of a public Instagram account; social_youtube when you need latest videos of a YouTube channel: video id, title, link. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "handle": "<handle>"
    },
    "name": "social_socialblade"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	Account handle without @, e.g. mrbeast
`platform`	No	youtube, instagram, tiktok or twitch (default youtube)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description adds context beyond the annotations: it discloses a residential-proxy access path, states that only roughly 15 days of daily history are publicly available, and notes that failed calls are not charged, which is useful cost/limit information. With readOnlyHint=true and openWorldHint=true already covering the safety profile, this is adequate, but it says nothing about rate limits, whether missing metrics are omitted or null, or latency/retry behavior.

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?

Purpose and scope are front-loaded in the first clause, followed by the data inventory, then the sibling routing, then pricing. It is a single dense paragraph, and the metric enumeration and proxy/payment tail run long, but every element carries information an agent would otherwise lack.

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?

For a two-parameter read tool with an output schema, the description still covers data coverage limits, sourcing, sibling routing, and the x402 payment model with per-call price and no-charge-on-failure. An agent has everything needed to decide, call it correctly, and understand cost exposure.

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 100%, and the schema already documents both parameters, including the handle format ('without @, e.g. mrbeast') and the platform values with a youtube default. The description repeats the platform list but adds no extra syntax, casing, or fallback guidance, so the baseline 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?

The description names a specific resource (Social Blade creator statistics) across four named platforms and enumerates exactly what data comes back: followers/subscribers, views/likes, uploads, engagement rate, grade, ranks, country, category, plus ~15 days of daily history. It explicitly separates itself from social_instagram and social_youtube, so an agent can pick this tool without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule with alternatives: use social_instagram for an engagement snapshot of a public Instagram account and social_youtube for latest videos (video id, title, link). The implicit condition — use this one when you want cross-platform aggregate creator stats from Social Blade — is clear from the contrast, leaving nothing to infer.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?