Skip to main content
Glama

reddit_user

Retrieve a Reddit user's profile and posts. Specify content type: overview, submitted, or comments.

Instructions

Get a Reddit user profile and posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYes
usernameYes
typeNooverview, submitted, comments
limitNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get a Reddit user profile and posts' but does not mention authentication requirements (needs access_token), rate limits, error handling, or how the 'type' parameter affects output. Minimal transparency.

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 a single short sentence, making it concise. However, it omits necessary details, making it inefficient for accurate tool selection. It could be restructured to include more context without adding length.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return structure (profile fields, post formats), how 'type' modifies the output, or the behavior of 'limit'. An agent using this tool would need additional knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (only 'type' has a description). The description adds 'Get a Reddit user profile and posts' which implies username identifies the user and access_token is for auth, but does not clarify 'limit' or 'type' beyond the schema. It fails to compensate for the low schema coverage.

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 'Get a Reddit user profile and posts,' specifying a verb and resource. However, it does not differentiate from sibling tools like reddit_read or reddit_search, which may also retrieve posts. The purpose is clear but lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., reddit_search for searching posts, reddit_read for reading posts). There are no exclusions, context, or examples to help an agent decide.

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/malamutemayhem/unclick'

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