SiteCheck Shop & Social

First page of top comments on one YouTube video: author

social_youtube_comments

Read-only

First page of top comments (about 20) on one YouTube video: author, verified/creator flags, text, like count text, reply count text and age text. Comments turned off or empty return an empty list. Reply threads and later pages are not returned. Related tools on this server, for a different need: social_youtube_hashtag when you need videos on one YouTube hashtag page: video id, title; social_youtube_channel_email when you need YouTube channel About page from YouTube's public page data. 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": {
      "videoId": "<videoId>"
    },
    "name": "social_youtube_comments"
  }
}

Input Schema

Name	Required	Description	Default
`videoId`	Yes	YouTube video id (11 characters)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses result cardinality (~20), pagination limits, the empty-list behavior when comments are disabled or empty, and an explicit billing model ($0.002 USDC per successful call via x402, failed calls not charged). Cost and failure-charging behavior are exactly the kind of operational context annotations cannot convey.

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?

The most useful content (what you get, what you don't, cost) is front-loaded in the first three sentences, and the sibling routing follows. The trailing sibling/pricing block is dense and semicolon-chained, which makes it slightly harder to scan than the opening, but no sentence is padding.

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 single-parameter read tool with an output schema, everything an agent needs is present: scope, cardinality, empty-result behavior, exclusions, alternatives, and cost. The output schema covers return values, so the description need not restate them further.

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?

There is a single required parameter with 100% schema description coverage ('YouTube video id (11 characters)'), so the schema already carries the semantics. The description adds no extra meaning about the id format or where to obtain it, which is the expected baseline-3 outcome for a fully documented single-parameter schema.

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?

States a specific verb and resource ('First page of top comments ... on one YouTube video') and enumerates the returned fields (author, verified/creator flags, text, like count, reply count, age). It is immediately distinguishable from siblings like social_youtube_hashtag or social_youtube_channel_email, and it explicitly bounds scope by excluding reply threads and later pages.

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?

It names two alternative tools with the condition that selects each ('when you need videos on one YouTube hashtag page', 'when you need YouTube channel About page'), which is real routing guidance. It also gives exclusions (no reply threads, no later pages) but does not point to any tool that would serve those needs, so the when-not side stops short of a full alternative map.

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?