SiteCheck Shop & Social

Posts of one subreddit from Reddit's public feed, sorted

social_reddit_posts

Read-only

Posts of one subreddit from Reddit's public feed, sorted hot, new, top or rising (about 25 items): id, title, author, date and link. The feed has no scores or comment counts, so it cannot rank by votes. Related tools on this server, for a different need: social_reddit_posts_comments when you need Reddit community discussions from Reddit's public RSS; 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

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": {
      "subreddit": "<subreddit>"
    },
    "name": "social_reddit_posts"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	hot, new, top or rising (default hot)
`subreddit`	Yes	Subreddit name without r/ (2-21 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

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the feed's limitation (no scores or comment counts, so it cannot rank by votes), the approximate result size (~25 items), and the pricing model ($0.002 USDC per successful call via x402 on Base/Solana/Arc, failed calls not charged). The cost and payment precondition 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?

Front-loaded with purpose and result shape, then alternatives, then price — a sensible order. Slightly padded by repeating 'Reddit's public feed'/'public user feed' within the alternatives clause, but no sentence is expendable.

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, so return-value detail is optional, yet the description still names the fields for quick scanning. It covers scope, limitations, alternatives, and payment prerequisites — nothing an agent needs before calling it 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 coverage is 100%, so the schema already documents both parameters including the sort enumeration and the subreddit name format. The description repeats the sort values but adds no format, default, or edge-case meaning beyond what the schema provides, 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?

States a specific verb+resource+scope: 'Posts of one subreddit from Reddit's public feed, sorted hot, new, top or rising (about 25 items)', plus the exact fields returned. An agent can distinguish it from social_reddit_posts_comments and social_reddit_profiles without opening any schema.

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?

Explicitly routes the agent to sibling tools with the condition that selects them ('when you need Reddit community discussions', 'when you need Reddit user profile'), which is strong routing guidance. It stops short of an explicit when-not-to-use statement for this tool itself, but the surrounding context makes the use case unambiguous.

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?