Skip to main content
Glama
eliasbiondo

Reddit MCP Server

by eliasbiondo

reddit_get_user_posts

Retrieve a Reddit user's submitted posts with options to filter by category, time window, and limit results for analysis or monitoring.

Instructions

Get a Reddit user's submitted posts.

Args: username: Reddit username without u/ prefix (e.g., 'spez') limit: Maximum number of posts (default: 25, max: 100) category: Listing category (hot, top, new). Default: new time_filter: Time window for top listings (hour, day, week, month, year, all). Default: all

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
limitNo
categoryNo
time_filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `reddit_get_user_posts` which executes the tool by calling the user service.
    async def reddit_get_user_posts(
        username: str,
        ctx: Context,
        limit: int = 25,
        category: str | None = None,
        time_filter: str | None = None,
    ) -> list[dict[str, Any]]:
        try:
            results = await service.get_user_posts(
                username, limit=limit, category=category, time_filter=time_filter
            )
            return McpSerializer.serialize_list(results)
        except Exception as e:
            McpErrorMapper.map(e, "reddit_get_user_posts")
  • Registration of the `reddit_get_user_posts` tool using the FastMCP decorator.
    @mcp.tool(
        name="reddit_get_user_posts",
        description=(
            "Get a Reddit user's submitted posts.\n\n"
            "Args:\n"
            "    username: Reddit username without u/ prefix "
            "(e.g., 'spez')\n"
            "    limit: Maximum number of posts "
            "(default: 25, max: 100)\n"
            "    category: Listing category (hot, top, new). "
            "Default: new\n"
            "    time_filter: Time window for top listings "
            "(hour, day, week, month, year, all). Default: all"
        ),
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.

Install Server

Other Tools

Latest Blog Posts

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