Reddit MCP Server

reddit_get_subreddit_posts

Fetch posts from a subreddit listing by name, with optional category, time filter, and result limit. Use it to browse hot, top, new, or rising Reddit content for a chosen community.

Instructions

Get posts from a subreddit listing.

Args: subreddit: Subreddit name without r/ prefix (e.g., 'Python', 'news') limit: Maximum number of posts (default: 25, max: 100) category: Listing category (hot, top, new, rising). Default: hot time_filter: Time window for top listings (hour, day, week, month, year, all). Default: all

Returns: An object with a 'posts' 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": {
      "subreddit": "<subreddit>"
    },
    "name": "reddit_get_subreddit_posts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`category`	No
`subreddit`	Yes
`time_filter`	No

Output Schema

Name	Required	Description	Default
`posts`	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 listings of posts (subreddit or user submissions)."

addedOutput schema / properties / posts

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

removedOutput schema / properties / result

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

changedOutput schema / required

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

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 load; it does disclose concrete behavioral facts (limit max 100, defaults of hot/all, the four listing categories). It omits auth requirements, rate limits, pagination behavior, and whether the call is read-only, which matters for a 0%-annotated tool.

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 one-line summary followed by tightly scoped Args/Returns blocks; each line earns its place. The opening sentence slightly restates the tool name but sets up the structured detail efficiently.

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

Completeness3/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 values need not be explained, and all four inputs are documented. However, for an unannotated network-backed read tool, missing auth/rate-limit/pagination context leaves it only adequately complete.

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

Parameters5/5

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

Schema coverage is 0% (no descriptions, no enums), so the description must compensate, and it does: every one of the four parameters gets an explanation, the valid category and time_filter values are enumerated, the limit ceiling is given, and the format for subreddit ('without r/ prefix') is clarified.

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 ('Get posts from a subreddit listing'), which is clearly distinct from search-oriented and user-oriented siblings. It does not explicitly name the alternatives, but the scope of a listing fetch is unambiguous.

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?

Usage is only implied by the parameter docs ('listing category', 'time window for top listings'). Nothing says when to prefer this over reddit_search or reddit_search_subreddit, and there are no stated prerequisites for the subreddit name.

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

Deploy Server