Skip to main content
Glama
Asynchronous-0x4C

Reddit Research MCP

reddit_get_my_activity

Read-only

Retrieve your recent Reddit posts and comments to gauge existing subreddit activity, avoid over-posting, and calculate the 9:1 self-promotion ratio.

Instructions

Fetch the user's own recent posts and comments. Used to judge how active they already are in a subreddit (so they do not over-post) and to compute the 9:1 self-promotion ratio. Results are capped; this does not page indefinitely.

This server is read-only. It cannot post, comment, vote, edit, delete, follow, or message on Reddit, and no such code exists in it. The user performs every Reddit action manually.

Prioritize genuinely helpful participation over product promotion. Do not rank a thread highly merely because it can be used to promote a product. Respect subreddit rules and surface uncertainty when rules are ambiguous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses that results are capped and do not page indefinitely, and that the server is read-only with no code path for mutations. This adds meaningful behavioral context an agent needs before calling it.

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?

The main purpose is front-loaded in the first sentence, and the read-only caveat is useful. The final paragraph contains general policy guidance that is not strictly tool-specific, adding minor noise, but the overall description remains reasonably concise.

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 a simple two-optional-parameter tool, the description covers purpose, usage context, cap behavior, and read-only constraints, and an output schema exists. The main gap is parameter semantics, but the parameter names and defaults make the tool reasonably invokable as-is.

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?

The input schema provides no descriptions for days or limit, and the tool description does not explicitly explain either parameter. 'Recent' and 'Results are capped' are only implicit hints, leaving the agent without clear semantics for the two parameters.

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 opens with 'Fetch the user's own recent posts and comments,' which is a specific verb plus resource. It also clarifies the tool's purpose by mentioning activity checks and the 9:1 self-promotion ratio, making it distinct from siblings like reddit_get_replies_to_me or reddit_get_thread.

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 explicitly says the tool is used to judge a user's activity in a subreddit and compute the 9:1 ratio, giving clear context for when to call it. It does not explicitly list alternatives or exclusions, but the intended use is clear enough for selection.

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

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/Asynchronous-0x4C/reddit-research-mcp'

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