Reddit data for agents

reddit_search_user

Paid ($0.002). Search user — Reddit. Live data as JSON. Pay with x402 or an Authorization: Bearer bby_live_... credits key.

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": {
      "keyword": "<keyword>"
    },
    "name": "reddit_search_user"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Optional.
`keyword`	Yes	Required.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 6, 2026

TDQS

C2.8/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral disclosure burden. It usefully discloses that the call is paid, returns live data as JSON, and requires payment via x402 or an Authorization Bearer key. However, it does not describe pagination behavior, response contents, or read-only safety, leaving notable gaps.

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 description is short and every clause contributes a distinct operational fact: cost, purpose, output format, and payment method. It could be better structured by leading with purpose, but it wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a paid tool with no output schema and no annotations, so the description should explain what the returned JSON contains and what keyword/cursor mean. It only says 'Live data as JSON' and vaguely refers to searching a user, leaving the agent unable to confidently predict the result or distinguish this from related sibling tools.

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 baseline is 3. Both parameters have minimal descriptions ('Required.' and 'Optional.'), and the tool description adds no extra meaning about how keyword is used or how cursor affects results. The description therefore does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Search user — Reddit,' which identifies a verb and resource, but it does not clarify whether the tool searches for user accounts by keyword, searches within a user's content, or returns user profile data. The sibling names help, but the description alone is vague about the exact purpose.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus siblings like reddit_search_post, reddit_user, or reddit_user_posts. The description only states cost and auth requirements, not selection criteria or exclusions.

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

All Reddit data for agents 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?