Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

A user's recent activity

get_user_activity
Read-onlyIdempotent

Inspect a Reddit account's public history—age, karma, recent posts and comments—to spot vendor staff, advocates, or single-topic accounts before weighting their advice.

Instructions

Show who is talking: account age, karma, and recent public posts and comments.

Ends the header with the subreddits the activity concentrates in, which helps spot vendor staff, advocates, or single-topic accounts before weighting their advice. Suspended accounts are reported as such; an account that is deleted or never existed returns a not-found error. It reads one account's public history; it cannot search users.

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_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNooverview (posts and comments), submitted (posts) or comments.overview
sortNonew (default, newest first), hot, top or controversial.new
timeNoTime window; applies to top and controversial only.all
afterNoCursor from a previous 'next: after=...' line.
limitNoItems, 1 to 100.
usernameYesReddit username; a u/ prefix or profile URL is fine.
body_charsNoCharacters of each body to show, 0 to 4000.
include_nsfwNoShow posts, comments and communities Reddit marks NSFW (18+). Off by default; hidden items are counted in the output. A server setting can keep them hidden even when true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: suspended accounts are reported as such, deleted or nonexistent accounts return a not-found error, and the header ends with a subreddit concentration summary. With no output schema, that return-shape detail is genuinely additive; only rate limits and pagination are left implicit (the 'after' cursor is documented in the schema instead).

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

Conciseness4/5

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

Front-loaded with what is returned, then use case, then error/scope behavior — good ordering and no filler. The second sentence ('Ends the header with the subreddits...') is awkwardly phrased and presumes a header structure the reader has not yet seen, which costs a little clarity.

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?

For an 8-parameter read tool with no output schema, the definition covers what is returned, the NSFW/error edge cases, and the scope limit. The only real gap is that return structure beyond the subreddit header is left vague, but the schema's cursor and body_chars parameters fill most of that.

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% and every enum, default, and range is documented inline, so the schema carries parameter meaning entirely. The description adds only a loose notion of recency and 'public posts and comments' without touching sort, time, limit, or NSFW handling — correct baseline for a fully documented schema, but no added value.

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?

States a specific verb and resource ('Show ... account age, karma, and recent public posts and comments') and closes with an explicit scope boundary: 'It reads one account's public history; it cannot search users.' That boundary alone separates it from search_reddit and search_subreddits without opening any schema.

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?

Gives a concrete decision context ('spot vendor staff, advocates, or single-topic accounts before weighting their advice') plus an exclusion ('cannot search users'). It stops short of naming a specific sibling to use instead for user search, so the alternative is implied rather than spelled out.

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