Reddit MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.2
Disambiguation3/5
The tools have clear distinctions between post retrieval, subreddit listing, user activity, and search operations, but there is some overlap between reddit_get_user and reddit_get_user_posts, as the former includes both posts and comments while the latter is a subset. This could cause confusion about which to use for specific user post queries.
Naming Consistency5/5
All tool names follow a consistent reddit_verb_noun pattern with snake_case throughout, such as reddit_get_post, reddit_get_subreddit_posts, and reddit_search_subreddit. This predictability makes it easy for agents to understand and navigate the toolset.
Tool Count5/5
With 6 tools, the server is well-scoped for a Reddit API, covering key functionalities like retrieving posts, subreddit content, user data, and search operations. This count is neither too sparse nor overwhelming, fitting typical use cases effectively.
Completeness4/5
The toolset covers essential read operations for posts, subreddits, users, and search, with good parameter support. However, it lacks write or interaction capabilities (e.g., posting, commenting, voting), which are common in Reddit workflows, leaving minor gaps that agents might need to work around.
Average 3.7/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- 1 of 4 community issues answered or closed in the last 6 months
- 0 commits in the last 12 weeks
- Last stable release on March 11, 2026
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It adequately discloses the comment tree inclusion (important behavioral trait not obvious from 'get post'), but omits auth requirements, rate limits, comment depth limits, and error handling for invalid permalinks.
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?
Well-structured with purpose front-loaded in the first sentence, followed by clear Args documentation. No redundant text; the example permalink efficiently illustrates the expected format without verbosity.
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?
Appropriate for a single-parameter read operation with output schema present. Covers core functionality and return data shape (comment tree), but given lack of annotations, should mention authentication requirements or API rate considerations to be complete.
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?
With 0% schema description coverage, the Args block compensates effectively by documenting the permalink parameter with both semantic description ('Reddit permalink path') and format example ('/r/Python/comments/abc123/my_post/'), clarifying expected input structure.
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?
Clear specific verb ('Get') + resource ('Reddit post') + scope ('full details including its comment tree'). Distinguishes implicitly from siblings via the permalink-based retrieval (vs. search/list operations), though explicit differentiation is absent.
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?
No explicit when-to-use guidance, prerequisites, or alternatives mentioned. User must infer this is for direct permalink retrieval versus searching or listing from sibling tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal context beyond parameter definitions. It omits pagination behavior, rate limits, authentication requirements, and whether results include deleted posts or comments (vs submissions only).
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?
Well-structured with a clear summary sentence followed by an Args block documenting parameters. No redundant prose. The docstring-style formatting is readable and efficient, though slightly informal compared to standard MCP description conventions.
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?
Adequate for parameter documentation given zero schema coverage, but incomplete overall. Missing critical context: no distinction from reddit_get_user (which may return comments vs submissions), no mention of the output schema structure, and no API behavioral constraints (e.g., Reddit's rate limiting for user history endpoints).
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?
Excellent compensation for 0% schema coverage: the Args section documents all 4 parameters with specific constraints (e.g., 'no u/ prefix', max 100), valid enum values (hot/top/new), and effective defaults. Score 4 (not 5) due to default value discrepancies: schema specifies null defaults for category/time_filter while description claims 'new' and 'all' respectively.
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?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('Reddit user's submitted posts'). It effectively distinguishes from siblings: unlike reddit_get_subreddit_posts (community content), reddit_get_post (single item), or reddit_get_user (profile metadata), this targets a specific user's submission history.
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?
No guidance is provided on when to use this tool versus alternatives like reddit_search (for query-based discovery) or reddit_get_subreddit_posts (for community browsing). There are no stated prerequisites, rate limit warnings, or conditions that would help an agent select this over sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With zero annotations, the description carries the full disclosure burden. It provides useful behavioral constraints (max 100 posts, default values, category options) and notes the time_filter applies only to 'top' listings. However, it omits authentication requirements, rate limits, read-only safety confirmation, or pagination behavior.
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?
Well-structured with purpose front-loaded in the first sentence followed by an Args block. While the Args block is lengthy, it is necessary given the empty schema. No wasted sentences; every line provides essential parameter documentation.
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?
Adequate for the tool's complexity given the output schema exists (covering return values). Parameter documentation is complete, but the description lacks operational context like API authentication requirements or rate limiting, which is crucial given no annotations are provided.
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?
Excellent compensation for 0% schema coverage. Documents all 4 parameters with concrete examples ('Python', 'news'), enum values (hot/top/new/rising), value constraints (max: 100), and formatting rules (without r/ prefix). This adds essential semantic meaning completely absent from 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 specific verb+resource ('Get posts from a subreddit listing') and implies bulk retrieval via 'listing', which distinguishes it from sibling 'reddit_get_post' (likely single post). However, it doesn't explicitly contrast with other siblings like 'reddit_search' or 'reddit_get_user_posts'.
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?
Provides no explicit guidance on when to use this tool versus siblings (e.g., when to use this vs reddit_search for finding posts). The only usage hint is implicit in the time_filter description noting it applies to 'top listings', but lacks 'when-not' or alternative recommendations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. The term 'Search' implies a read-only operation, which is helpful, but the description lacks disclosure of rate limits, authentication requirements, error behaviors (e.g., private/quarantined subreddits), or what content types are returned. The existence of an output schema mitigates some return-value disclosure needs.
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 efficiently structured with a clear purpose statement front-loaded ('Search within a specific subreddit'), followed by a well-formatted Args section. Every sentence earns its place. Minor deduction only because the Args documentation is slightly verbose, though necessary given the schema's lack of descriptions.
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 the 0% schema coverage, the description successfully documents all 4 parameters with examples and constraints. The presence of an output schema means return values don't need explanation in the description. It adequately covers the tool's scope, though it could mention error cases or sibling distinctions for completeness.
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?
Excellent compensation for 0% schema description coverage. The Args section adds crucial semantics: 'subreddit' includes format guidance ('without r/ prefix') and examples, 'limit' specifies constraints (default: 25, max: 100), and 'sort' enumerates valid options. This provides complete semantic meaning that the schema totally lacks.
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?
The description clearly states the verb ('Search') and resource ('subreddit'), and the phrase 'within a specific subreddit' effectively distinguishes it from the sibling 'reddit_search' tool (which presumably searches all of Reddit). However, it doesn't specify what content type is being searched (posts, comments, etc.), preventing a 5.
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 description implies usage context by requiring a 'subreddit' parameter, suggesting this is for targeted single-community searches. However, it lacks explicit guidance on when to prefer this over 'reddit_search' (global search) or 'reddit_get_subreddit_posts' (listing vs. searching), and doesn't mention prerequisites like subreddit existence or access requirements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry full behavioral burden. It discloses the maximum results limit (100) and available sort options, which is helpful. However, it omits rate limiting information, authentication requirements, and pagination behavior details that would be valuable for a search API 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?
Efficient three-part structure: purpose statement followed by Args documentation. Every sentence provides value. The Args format is slightly rigid compared to prose, but remains highly readable and wastes no 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 the simple 3-parameter schema, presence of output schema, and clear scope definition, the description provides sufficient context. It appropriately delegates return value details to the output schema while covering search scope and parameter semantics adequately.
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?
With 0% schema description coverage, the description fully compensates by documenting all three parameters in the Args section: query includes concrete examples ('python web scraping'), limit specifies constraints (default: 25, max: 100), and sort enumerates valid options (relevance, hot, top, etc.).
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?
Clear specific verb ('Search'), resource ('Reddit/posts'), and scope ('all of Reddit'). The phrase 'all of Reddit' effectively distinguishes this from sibling subreddit-specific tools like reddit_search_subreddit and reddit_get_subreddit_posts.
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?
Provides implied usage through scope specification ('all of Reddit'), allowing inference that this is for global searches versus subreddit-specific queries. However, lacks explicit 'when to use' guidance comparing it to reddit_search_subreddit or prerequisites like query formatting requirements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It successfully discloses 'public' visibility scope, 'recent' temporal limitation, and rate constraints (max: 100). However, lacks information on authentication requirements, error handling (e.g., non-existent user), or pagination behavior.
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?
Efficient two-section structure: single-sentence purpose statement followed by Args block. Every sentence earns its place with no repetition of structured data. Front-loaded with the core verb and resource.
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 presence of output schema, description appropriately omits return value details. Parameter documentation is complete despite 0% schema coverage. Minor gap: could explicitly clarify relationship with reddit_get_user_posts sibling to maximize tool selection accuracy.
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?
With 0% schema description coverage, the description fully compensates by providing detailed semantics for both parameters: username format explicitly excludes 'u/' prefix with clear examples ('spez', 'GallowBoob'), and limit documents default value (25), maximum constraint (100), and semantics ('Maximum number of activity items').
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?
Specific verb 'Get' with clear resource 'Reddit user's recent public activity'. Critically, it explicitly includes '(posts and comments)' which distinguishes it from sibling tool 'reddit_get_user_posts' that presumably returns only posts, fulfilling the sibling differentiation requirement for a 5.
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?
Provides implied usage guidance by specifying it retrieves both content types (posts and comments), hinting at when to use this versus the posts-only sibling. However, lacks explicit 'when to use/when not to use' statements or direct references to sibling alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![reddit-mcp-server MCP server](https://glama.ai/mcp/servers/eliasbiondo/reddit-mcp-server/badges/card.svg)](https://glama.ai/mcp/servers/eliasbiondo/reddit-mcp-server)

Score Badge

Copy to your README.md:

[![reddit-mcp-server MCP server](https://glama.ai/mcp/servers/eliasbiondo/reddit-mcp-server/badges/score.svg)](https://glama.ai/mcp/servers/eliasbiondo/reddit-mcp-server)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliasbiondo/reddit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server