SiteCheck Shop & Social

Reddit community discussions from Reddit's public RSS

social_reddit_posts_comments

Read-only

Reddit community discussions from Reddit's public RSS feeds: top posts of a subreddit for hour/day/week/month/year/all, or one thread (post id) with its visible comments. Feeds carry title, author, link, date and text only; no scores or comment counts. Reddit may rate-limit (503). 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_profiles when you need Reddit user profile from Reddit's public user feed. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "social_reddit_posts_comments"
  }
}

Input Schema

Name	Required	Description
`post`	No	Optional Reddit post id (e.g. 1x9uihs). When set, returns that thread and its comments
`period`	No	hour, day, week, month, year or all (default day). Used for the listing
`subreddit`	No	Subreddit name without r/ (2-21 letters, digits or _). Default technology

Output Schema

Name	Required	Description	Default
`posts`	No
`period`	No
`source`	No
`checkedAt`	No
`postCount`	No
`subreddit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that feeds carry only title, author, link, date and text, with no scores or comment counts, and it warns that Reddit may rate-limit with 503. It also states the price ($0.002 USDC per successful call, x402 on Base/Solana/Arc) and that failed calls are not charged, which is exactly the kind of cost and failure context an agent needs.

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?

It is front-loaded with the capability, then limits, then alternatives, then price, so every sentence carries information. The dense semicolon-chained sentences in a single paragraph make scanning slightly harder than it needs to be.

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 read-only RSS-backed fetch with a full schema and an output schema, the description covers data limits, rate limits, and cost, which are the real unknowns. The one remaining gap is how the optional post parameter interacts with subreddit and period when both are supplied.

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%, so the schema already documents post, period, and subreddit semantics including the default day and the default technology subreddit. The description restates the mode behavior of post but adds no format or interaction details beyond the schema, so the baseline 3 applies; notably it does not say what happens if post is supplied alongside period/subreddit.

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 names a specific verb and resource: top posts of a subreddit for a given period, or one thread (post id) with its visible comments. It names the sibling tools social_reddit_posts and social_reddit_profiles, but the boundary against social_reddit_posts ('posts of one subreddit from Reddit's public feed, sorted') is nearly identical to this tool's listing mode, which leaves the split unclear.

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 gives explicit when-to-use routing between three Reddit tools and explains that setting post switches from listing to thread mode. The exclusions are present but the practical difference from social_reddit_posts is stated only as 'sorted', which is thin given how closely the two overlap.

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?