Skip to main content
Glama
karanb192

Reddit Buddy MCP

by karanb192
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

user_analysis

Read-only

Analyze a Reddit user's posting history, karma, and activity patterns. Returns posts, comments, and statistics.

Instructions

Analyze a Reddit user's posting history, karma, and activity patterns. Returns posts, comments, and statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesReddit username without u/ prefix
time_rangeNoTime range for posts/comments (default: month). Note: When set to values other than "all", posts are sorted by top scores within that period. When set to "all", posts are sorted by newestmonth
posts_limitNoDefault 10, range (0-100). Change ONLY IF user specifies.
comments_limitNoDefault 10, range (0-100). Override ONLY IF user asks.
top_subreddits_limitNoDefault 10, range (1-50). Change ONLY IF user requests.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed16 schema fields changedv1.1.14
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / comments_limit / default
      Added value: +10
    • changedInput schema / properties / comments_limit / description
      Previous value: -"Number of recent comments to include (0-100, default: 10)"New value: +"Default 10, range (0-100). Override ONLY IF user asks."
    • addedInput schema / properties / comments_limit / maximum
      Added value: +100
    • addedInput schema / properties / comments_limit / minimum
      Added value: +0
    • addedInput schema / properties / posts_limit / default
      Added value: +10
    • changedInput schema / properties / posts_limit / description
      Previous value: -"Number of recent posts to include (0-100, default: 10)"New value: +"Default 10, range (0-100). Change ONLY IF user specifies."
    • addedInput schema / properties / posts_limit / maximum
      Added value: +100
    • addedInput schema / properties / posts_limit / minimum
      Added value: +0
    • addedInput schema / properties / time_range / default
      Added value: +"month"
    • changedInput schema / properties / time_range / description
      Previous value: -"Period to analyze: \"day\", \"week\", \"month\", \"year\", \"all\". Note: \"all\" returns newest content, others return top-scored content from that period"New value: +"Time range for posts/comments (default: month). Note: When set to values other than \"all\", posts are sorted by top scores within that period. When set to \"all\", posts are sorted by newest"
    • addedInput schema / properties / top_subreddits_limit / default
      Added value: +10
    • changedInput schema / properties / top_subreddits_limit / description
      Previous value: -"Number of most-active subreddits to list (1-50, default: 10)"New value: +"Default 10, range (1-50). Change ONLY IF user requests."
    • addedInput schema / properties / top_subreddits_limit / maximum
      Added value: +50
    • addedInput schema / properties / top_subreddits_limit / minimum
      Added value: +1
    • changedInput schema / properties / username / description
      Previous value: -"Reddit username without u/ prefix (e.g., \"spez\", not \"u/spez\")"New value: +"Reddit username without u/ prefix"
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations include readOnlyHint=true, and the description aligns with that. Additional behavioral details are provided in the parameter description (time_range sorting behavior) but no further safety or side-effect context beyond what annotations already convey.

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 two sentences, front-loading the purpose with no superfluous information. Every word serves a clear function.

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 absence of an output schema, the description provides a reasonable overview of what is returned (posts, comments, statistics). However, it could be more explicit about the exact statistics or structure returned.

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?

Schema description coverage is 100%, so the schema already documents parameters. The tool description adds no extra parameter insights beyond the schema, but includes a helpful note on time_range sorting behavior in the parameter description itself.

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 'Analyze a Reddit user's posting history, karma, and activity patterns' with a specific verb and resource. It distinguishes from siblings like browse_subreddit or search_reddit by focusing on a single user's data.

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 implies when to use (when analyzing a user), but it does not explicitly state when not to use or mention alternatives. However, sibling names provide implicit differentiation.

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

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