Skip to main content
Glama

get_user_activity

Read-onlyIdempotent

Retrieve a Reddit user's recent posts and comments, newest first, with overview/posts/comments selection, result limits, cursor pagination, and live or archive source options.

Instructions

A user's recent posts and/or comments, newest first.

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
kindNoposts, comments, or bothoverview
limitNo
cursorNonext_cursor from a previous call
sourceNoData source. 'auto' tries live reddit.com (if a session cookie is configured) and falls back to the Arctic Shift archive; 'live' or 'archive' forces one.auto
usernameYesUsername, with or without u/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the useful ordering trait 'newest first', but says nothing about pagination behavior, result caps, or what happens when the live source is unavailable — the source fallback is only explained in the schema, not the description.

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?

A single front-loaded sentence with no filler, and the ordering constraint is placed where an agent will see it immediately. It is lean to the point of leaving gaps, but nothing in it is wasted.

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?

For a five-parameter, paginated, dual-source tool, the description covers identity and ordering but omits pagination guidance and source trade-offs that an agent needs to call it well. Annotations and the rich schema absorb much of the burden, so it is adequate rather than deficient.

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 coverage is 80%, so the schema already documents kind, cursor, and source in detail. The description's 'and/or' loosely signals the kind parameter but adds no meaning beyond that, so the baseline 3 applies.

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 names a specific resource (a user's posts and/or comments) and a concrete retrieval behavior (newest first), so an agent can tell it apart from siblings like get_post or get_comment_thread. It stops short of naming any sibling to route against, which keeps it out of 5 territory.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer from the title alone that this is the tool for per-user activity rather than search_posts or browse_subreddit.

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