scout-mcp

reddit_search

Search Reddit public feeds for posts and discussions by keyword, subreddit, sort, and time range. Returns titles, scores, comments, and content previews to analyze community sentiment, user experiences, and real-world feedback.

Instructions

Search Reddit for posts and discussions using public JSON feeds (no API key required). Returns title, score, comments, subreddit, and content preview. Great for community sentiment, user experiences, and real-world feedback. Rate limit: 10 req/min.

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": {
      "query": "<query>"
    },
    "name": "reddit_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query
`per_page`	No	Results per page (max 25)
`sort`	No	Sort order	relevance
`time`	No	Time filter	week
`subreddit`	No	Restrict search to a specific subreddit (e.g. 'programming')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Description discloses behavioral traits: uses public JSON feeds, no API key required, returns specific fields, and rate limit. Since annotations are absent, description carries full burden for transparency; it provides good detail without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise with three front-loaded sentences: what it does (first), what it returns (second), and usage context/rate limit (third). No wasted words.

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?

Given no output schema, the description adequately covers return fields. Tool complexity is moderate with 5 parameters and 1 required. The description provides enough context for effective use, though it could mention handling of empty results or pagination for completeness.

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% with descriptions for each parameter. The description adds value by listing returned fields (title, score, comments, etc.) and stating 'no API key required', which helps parameter usage context. However, it doesn't add extra semantic details beyond schema for individual parameters, so baseline 3 is appropriate.

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?

Description clearly states the tool searches Reddit posts/discussions using public JSON feeds. It distinguishes from sibling search tools (e.g., arxiv_search, x_search) by specifying Reddit as the source and noting no API key required.

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?

Description provides clear context for when to use (community sentiment, user experiences, real-world feedback) and mentions rate limit (10 req/min). However, it does not explicitly state when not to use or compare to sibling tools.

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