Skip to main content
Glama
eliasbiondo

Reddit MCP Server

by eliasbiondo

reddit_get_user

Retrieve a Reddit user's recent public posts and comments to analyze their activity and contributions across the platform.

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)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the 'reddit_get_user' MCP tool, which delegates to the user_service and handles serialization and errors.
    @mcp.tool(
        name="reddit_get_user",
        description=(
            "Get a Reddit user's recent public activity "
            "(posts and comments).\n\n"
            "Args:\n"
            "    username: Reddit username without u/ prefix "
            "(e.g., 'spez', 'GallowBoob')\n"
            "    limit: Maximum number of activity items "
            "(default: 25, max: 100)"
        ),
    )
    async def reddit_get_user(
        username: str,
        ctx: Context,
        limit: int = 25,
    ) -> list[dict[str, Any]]:
        try:
            results = await service.get_user(username, limit=limit)
            return McpSerializer.serialize_list(results)
        except Exception as e:
            McpErrorMapper.map(e, "reddit_get_user")
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.

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