Reddit MCP Server

get_my_overview

Read-only

Fetch the authenticated user's recent posts and comments in a single newest-first feed. Supports pagination using an after cursor.

Instructions

Get the authenticated user's own recent activity — posts and comments interleaved, newest first. Read-only but requires user credentials (REDDIT_USERNAME/REDDIT_PASSWORD). Returns up to limit items plus an after cursor for the next page. Use get_my_saved for saved items, or get_user_posts / get_user_comments for another user. Do NOT use this to fetch a specific post's thread — use get_post_comments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_overview"
  }
}

Input Schema

Name	Required	Description	Default
`after`	No	Forward pagination cursor: the `after` value returned by a previous call. Omit for the first page.
`limit`	No	How many activity items to return, 1–100 (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.3Aug 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavioral context: credentials are required, the result is interleaved posts/comments in newest-first order, and pagination uses an `after` cursor. No contradiction with annotations exists.

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 short, front-loaded with the purpose, and every sentence contributes useful information — scope, credentials, return behavior, and explicit sibling alternatives. No redundant or vague wording.

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?

No output schema exists, but the description communicates the essential return semantics: up to `limit` items, posts and comments interleaved, newest first, with an `after` cursor. It could arguably describe item fields in more detail, but for this tool the provided context is reasonably complete.

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 100%, with both `limit` and `after` already well-described. The description reinforces their meaning by mentioning the pagination cursor and item limit, but it does not add substantive parameter semantics beyond what the schema already provides.

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 specifies a concrete action and scope: fetching the authenticated user's own recent activity, interleaving posts and comments, newest first. It also explicitly distinguishes this from get_my_saved, get_user_posts, get_user_comments, and get_post_comments.

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

Usage Guidelines5/5

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

The description provides clear when-to-use guidance: use get_my_saved for saved items, get_user_posts/get_user_comments when targeting another user, and do NOT use this tool for a specific post's thread — use get_post_comments instead.

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