SiteCheck Shop & Social

Reddit user profile from Reddit's public user feed

social_reddit_profiles

Read-only

Reddit user profile from Reddit's public user feed: the user's name, the profile subtitle, and their latest submitted posts (title, subreddit, date, link; about 25 items). No karma, account age or hidden profile data; the feed does not show them. Related tools on this server, for a different need: social_reddit_posts when you need posts of one subreddit from Reddit's public feed, sorted; social_reddit_posts_comments when you need Reddit community discussions from Reddit's public RSS. 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": {
      "username": "<username>"
    },
    "name": "social_reddit_profiles"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Reddit username without u/ (3-20 letters, digits, _ or -)

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

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real value on top by disclosing the result shape (~25 items), explicitly bounding the data that will NOT be returned, and explaining the billing model including that failed calls are free. The only gap is any hint about rate limits or pagination depth beyond the approximate item count.

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 purpose and payload are front-loaded, followed by exclusions, sibling routing, and pricing in a logical order with no repetition. The pricing sentence is somewhat verbose relative to its decision value, keeping this just below a top score.

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 one-parameter read tool this is fully adequate: it covers what fields come back, what is deliberately absent, which sibling to use instead, and the cost model. An output schema also exists, so no further return-value explanation is required.

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?

With a single parameter at 100% schema coverage, the schema already specifies the format (no u/ prefix, 3-20 letters/digits/_/-). The description adds no additional meaning about the username parameter, 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?

The description names a specific verb-less but precise resource: a Reddit user profile drawn from Reddit's public user feed, and enumerates the exact payload (name, subtitle, latest submitted posts with title, subreddit, date, link, ~25 items). It is immediately distinguishable from social_reddit_posts and social_reddit_posts_comments, which are explicitly named.

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 goes beyond a general context statement by naming two concrete alternatives with the selecting condition for each: social_reddit_posts for sorted posts of a single subreddit, and social_reddit_posts_comments for community discussions from RSS. It also sets an expectation boundary (no karma, account age, or hidden profile data), telling the agent when this tool's answer will be insufficient.

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?