Reddit MCP Server

reddit_get_user

Retrieve a Reddit user's recent public posts and comments by username. Use it to review someone's activity without API keys.

Instructions

Get a Reddit user's recent public activity (posts and comments).

Args: username: Reddit username without u/ prefix (e.g., 'spez', 'GallowBoob') limit: Maximum number of activity items (default: 25, max: 100)

Returns: An object with an 'items' array of posts and comments.

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": {
      "username": "<username>"
    },
    "name": "reddit_get_user"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`username`	Yes

Output Schema

Name	Required	Description	Default
`items`	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 a user's activity feed (posts and comments)."

addedOutput schema / properties / items

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: +[
+  "items"
+]

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

First observedv0.1.2Mar 24, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations, so the description carries the full burden. It does add useful traits such as 'recent' and 'public' (implying no private/draft data), but omits auth requirements, rate limits, ordering, and how far back 'recent' reaches.

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 purpose followed by compact Args and Returns sections. The Returns block largely restates what the output schema already provides, a small amount of redundancy, but nothing is padded elsewhere.

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?

For a two-parameter read tool with an output schema, the description covers the essentials: argument formats, limits, and return shape. It could say more about ordering/pagination and the posts-vs-comments distinction, but nothing critical for invocation is missing.

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%, yet the description compensates well: it specifies that username must omit the u/ prefix with concrete examples, and gives limit's default of 25 and max of 100, neither of which is captured in the schema.

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 (Get) and resource (a Reddit user's recent public activity) and clarifies the payload is posts and comments. It distinguishes itself somewhat from reddit_get_user_posts by including comments, but never names or contrasts the sibling explicitly.

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?

No explicit when-to-use statement or exclusions. The contrast with reddit_get_user_posts is only implied by the phrase 'posts and comments' in the parenthetical, leaving the agent to infer which sibling to pick.

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

Deploy Server