Skip to main content
Glama
Arindam200

Reddit MCP Server

get_user_posts

Retrieve a Reddit user's post history with options to sort by new, hot, top, or controversial content and filter by time period.

Instructions

Get a user's post/submission history.

Args:
    username: The username of the Reddit user (with or without 'u/' prefix)
    sort: Sort order for posts - one of: "new", "hot", "top", "controversial"
    time_filter: Time period to filter posts (e.g. "hour", "day", "week", "month", "year", "all")
    limit: Number of posts to return (1-100)

Returns:
    Dictionary containing structured post history with the following structure:
    {
        'username': str,  # The username
        'sort': str,  # Sort method used
        'time_filter': str,  # Time filter used
        'posts': [  # List of posts
            {
                'id': str,  # Post ID
                'title': str,  # Post title
                'author': str,  # Author's username
                'subreddit': str,  # Subreddit name
                'score': int,  # Post score (upvotes - downvotes)
                'upvote_ratio': float,  # Ratio of upvotes to total votes
                'num_comments': int,  # Number of comments
                'created_utc': float,  # Post creation timestamp
                'url': str,  # Full URL to the post
                'permalink': str,  # Relative URL to the post
                'is_self': bool,  # Whether it's a self (text) post
                'selftext': str,  # Content of self post (if any)
                'link_url': str,  # URL for link posts (if any)
                'domain': str,  # Domain of the linked content
                'over_18': bool,  # Whether marked as NSFW
                'spoiler': bool,  # Whether marked as spoiler
                'stickied': bool,  # Whether stickied in the subreddit
                'locked': bool,  # Whether comments are locked
                'distinguished': Optional[str],  # Distinguishing type (e.g., 'moderator')
                'gilded': int,  # Number of times gilded
            },
            ...
        ],
        'metadata': {
            'fetched_at': float,  # Timestamp when data was fetched
            'post_count': int,  # Number of posts returned
        }
    }

Raises:
    ValueError: If username is invalid, sort method is invalid, or time_filter is invalid
    RuntimeError: For other errors during the operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
sortNonew
time_filterNoall
limitNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so effectively. It describes the return structure in detail, specifies error conditions with 'Raises' (ValueError for invalid inputs, RuntimeError for other errors), and mentions the data fetching timestamp. However, it doesn't cover rate limits, authentication needs, or pagination behavior, leaving some gaps.

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 well-structured with clear sections (Args, Returns, Raises) and front-loads the core purpose. However, the detailed return structure explanation is lengthy; while informative, it could be more concise by summarizing key fields rather than listing all 20+ attributes, especially since there's no output schema.

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 tool's moderate complexity (4 parameters, no annotations, no output schema), the description is mostly complete. It covers purpose, parameters, return structure, and errors. However, it lacks information on behavioral aspects like rate limits, authentication requirements, and whether the tool is read-only or has side effects, which would enhance 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?

The description adds significant value beyond the input schema, which has 0% description coverage. It explains each parameter's purpose: 'username' accepts Reddit usernames with or without prefix, 'sort' lists valid options, 'time_filter' specifies time periods, and 'limit' defines the range (1-100). This compensates fully for the schema's lack of descriptions.

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 ('user's post/submission history'), making it immediately understandable. It distinguishes itself from siblings like 'get_user_comments' (which focuses on comments) and 'get_user_info' (which provides profile information), establishing a clear functional boundary.

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 through parameter explanations but doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't compare with 'search_posts' (which might search across users) or 'get_top_posts' (which might get popular posts regardless of user). The guidance is functional but lacks explicit contextual boundaries.

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/Arindam200/reddit-mcp'

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