Skip to main content
Glama
Sign In
reddirect

reddirect

by jeebus87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get User Profile

get_user_profile

Retrieve a Reddit user's public profile data, including karma breakdown and account age, by providing their username without the u/ prefix.

Instructions

Get a Reddit user's public profile including karma breakdown and account age.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "get_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesReddit username without u/ prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only repeats the purpose and adds no details on authentication, rate limits, error cases (e.g., nonexistent user), or whether the tool is safe to call repeatedly. This is insufficient for a tool with no output schema.

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?

The description is a single sentence, front-loading the tool's purpose. No wasted words; every part is necessary and informative.

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?

Given the tool's simplicity (one required parameter, no output schema), the description is adequate but not thorough. It mentions the profile includes karma breakdown and account age, but doesn't confirm other fields or error conditions. Slightly below ideal completeness.

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

Parameters3/5

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

Input schema coverage is 100%, and the schema already describes the 'username' parameter. The description adds no additional semantic meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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: get a Reddit user's public profile. It specifies the resource (Reddit user) and the contents (karma breakdown and account age). This distinguishes it from sibling tools like browse_subreddit or get_subreddit_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use this tool (to retrieve a user's public profile). However, it does not explicitly mention when not to use it or suggest alternatives, which would be helpful given the numerous sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools