Skip to main content
Glama
Arindam200

Reddit MCP Server

get_user_info

Retrieve Reddit user profile data including karma scores, account details, and moderation status by providing a username.

Instructions

Get information about a Reddit user.

Args:
    username: The username of the Reddit user to get info for

Returns:
    Dictionary containing user information with the following structure:
    {
        'username': str,  # User's username
        'created_utc': float,  # Account creation timestamp
        'comment_karma': int,  # User's comment karma
        'link_karma': int,  # User's post/link karma
        'has_verified_email': bool,  # Whether email is verified
        'is_mod': bool,  # Whether user is a moderator
        'is_gold': bool,  # Whether user has Reddit premium
        'has_subscribed': bool,  # Whether user has subscribed to premium
        'is_employee': bool,  # Whether user is a Reddit employee
        'over_18': bool,  # Whether user is marked as NSFW
        'is_suspended': bool,  # Whether account is suspended
        'suspension_expiration_utc': Optional[float],  # When suspension ends if suspended
        'total_karma': int,  # Total karma (comments + posts)
        'subreddit': Optional[Dict],  # User's profile subreddit info if exists
    }

Raises:
    ValueError: If the username is invalid or not found
    RuntimeError: For other errors during the operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYes
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 by documenting the return structure, error conditions (ValueError for invalid usernames, RuntimeError for other errors), and the specific data fields included. It provides comprehensive behavioral context beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized but not optimally structured. While the initial sentence clearly states the purpose, the detailed return structure documentation (while valuable) makes it somewhat dense. Every sentence earns its place, but the information could be more front-loaded with the core purpose emphasized before the detailed return format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 (single parameter, no output schema, no annotations), the description provides complete context. It covers purpose, parameter meaning, return structure with all fields documented, and error conditions. For a read-only data retrieval tool, this is comprehensive and leaves no significant gaps for agent understanding.

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?

The description adds significant value beyond the input schema, which has 0% description coverage. It explains that the 'username' parameter refers to 'The username of the Reddit user to get info for,' providing essential semantic context that the schema's title alone doesn't convey. For a single parameter with no schema descriptions, this is highly valuable.

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 ('information about a Reddit user'), distinguishing it from siblings like get_user_comments or get_user_posts which retrieve different types of user data. It precisely defines what information is retrieved rather than just restating the tool name.

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 get_user_comments or get_user_posts, nor are there any prerequisites or contextual usage instructions mentioned. The description only explains what the tool does, not when it should be selected over other available 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/Arindam200/reddit-mcp'

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