Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Reddit subreddit posts

reddit_subreddit_posts_list
Read-onlyIdempotent

List posts from a specified subreddit by hot, new, top, best, or rising without keyword filtering. Browse community feeds and paginate results with a cursor.

Instructions

List a subreddit's post feed (hot/new/top, no keyword) — use reddit_subreddit_search_list to search within it by keyword. Requires subreddit. Returns a list (use cursor when paginated).

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": {
      "subreddit": "<subreddit>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "reddit_subreddit_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOptional sort order for the returned posts.
cursorNoOpaque pagination cursor from a previous response.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
subredditYesSubreddit name, optional `r/` prefix, or Reddit subreddit URL. Must match Reddit's exact casing. Lists posts for this subreddit.
timeframeNoOptional timeframe used only when `sort` is `top`. Ignored/rejected for other sorts.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful operational hints — no keyword filtering and cursor-based pagination — but says nothing about auth requirements, rate limits, or result size, so it is an incremental rather than substantial addition.

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?

Two short sentences with the routing rule front-loaded and zero padding. 'Returns a list' is mild filler since a list tool obviously returns a list, but the trailing pagination note earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with full schema coverage and no output schema, the definition covers purpose, the required subreddit, the sibling alternative, and pagination behavior. The remaining parameters (context, llm_model, conversation_id) are self-documenting boilerplate in the schema.

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 all seven parameters including sort, timeframe, cursor, and subreddit casing rules are already documented in the schema. The description's parenthetical 'hot/new/top' partially echoes sort but omits the enum's 'best' and 'rising' and never mentions timeframe, so it adds little and is slightly incomplete relative to the schema.

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 ('List a subreddit's post feed') and immediately scopes it as a non-keyword feed with sort variants, which cleanly separates it from reddit_subreddit_search_list. An agent can pick between the two without opening either 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 an explicit routing rule: use reddit_subreddit_search_list when a keyword is involved, otherwise this feed tool. It is clear context with one named exclusion, though it does not state when a feed listing is inappropriate (e.g., needing a single post or comments).

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

Deploy Server

Other Tools