Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Reddit subreddit

reddit_subreddit_search_list
Read-onlyIdempotent

Search posts within a single subreddit by query, sort order, and timeframe. Returns paginated results so you can find relevant discussions inside one community.

Instructions

Search posts within one subreddit (not site-wide — use reddit_search_list for that). Requires subreddit. Returns a list (use cursor when paginated). Sort with sort (relevance, hot, top, new or comments), not sortBy.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for search results. Default: `relevance`.
queryNoSearch text to match against public subreddit posts.
cursorNoOpaque pagination cursor returned by 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. Searches posts within this subreddit.
timeframeNoTime range filter for search results. Default: `all`.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds modest behavior context by stating it returns a list and that a cursor handles pagination. It does not describe result shape, ranking semantics, or limits, so it goes slightly beyond annotations but not richly.

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?

Three compact sentences, front-loaded with scope and the sibling exclusion, then requirements, then return/pagination and sorting notes. No redundant phrasing; every clause carries actionable information.

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 description covers scope, required input, pagination and sorting adequately. It omits any hint about the sequencing constraint around `conversation_id` and parallel calls, though the schema itself explains that in detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds a genuinely non-schema detail: sort values go in `sort`, not `sortBy`, which pre-empts a likely wrong-argument error. It also restates the required `subreddit` and the cursor's pagination role, adding marginal value on top of 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?

Names a specific verb and resource ('Search posts within one subreddit') and immediately bounds the scope against the site-wide sibling. An agent can distinguish it from reddit_search_list without inspecting 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 Guidelines5/5

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

Explicitly states the when-not case ('not site-wide — use reddit_search_list for that') and names the required 'subreddit' input as a precondition. The alternative is named with the condition that selects it, leaving nothing to inference.

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