Reddit MCP Server

reddit_search

Search Reddit for posts matching a keyword query and retrieve sorted results with configurable limits for content research.

Instructions

Search all of Reddit for posts matching a query.

Args: query: Search keywords (e.g., 'python web scraping', 'machine learning') limit: Maximum number of results to return (default: 25, max: 100) sort: Sort order for results (relevance, hot, top, new, comments)

Returns: An object with a 'results' array.

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
`sort`	No
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.2.1Oct 27, 2026

addedOutput schema / description

Added value: +"Tool response for search queries."

removedOutput schema / properties / result

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "results"
+]

removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.1.2Mar 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden: it does disclose useful behavioral constraints such as the default limit of 25 and maximum of 100, which is real added context. It says nothing about authentication, rate limits, or pagination behavior, which matters for a live external search API.

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?

Front-loaded one-line purpose followed by compact Args/Returns sections with zero filler. Every line carries information the caller needs, and the structure maps cleanly onto the three parameters.

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?

An output schema exists, so the brief 'results' array note is sufficient and the description needn't detail return fields. For a three-parameter read tool with no annotations, what remains missing is minor: pagination/cursor guidance and any auth or rate-limit preconditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it largely does: query gets an example, limit gets default and max, and sort enumerates the accepted values ('relevance, hot, top, new, comments') that the schema only types as an unconstrained string. The sort values are the strongest addition since the schema provides no enum.

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?

States a specific verb and resource ('Search all of Reddit for posts') with the scope word 'all' that implicitly distinguishes it from the sibling reddit_search_subreddit. It never names the sibling explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The phrase 'all of Reddit' implies the tool is for site-wide searches rather than subreddit-scoped ones, which is useful against the sibling list. However, there is no explicit when-to-use/when-not statement and no guidance on choosing sort modes or limit tradeoffs.

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

Deploy Server