Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Reddit posts

reddit_search_list
Read-onlyIdempotent

Search Reddit posts site-wide by keyword, filter by timeframe, and sort results by relevance, new, top, or comment count. Use pagination cursors to retrieve additional matching posts.

Instructions

Search Reddit posts site-wide by keyword (not scoped to one subreddit — use reddit_subreddit_search_list for that). Requires query. Returns a list (use cursor when paginated). There is no subreddit field. Sort with sortBy: relevance, new, top or comment-count.

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

Input Schema

NameRequiredDescriptionDefault
trimNoWhether to request a smaller response shape when available.
queryYesRequired. Search query text for public Reddit posts.
cursorNoOpaque pagination cursor returned by a previous response.
sortByNoOptional sort order for search results. `comment-count` puts the most-commented posts first.
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.
timeframeNoOptional time range filter for search results.
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
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. Beyond that, the description adds return shape ('Returns a list') and pagination guidance ('use cursor when paginated'), which is useful context an agent would not know from annotations alone.

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 dense sentences, front-loaded with scope and alternative routing. Every clause conveys a distinct constraint or navigation cue with no filler.

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 open-world search tool with a fully documented schema and rich annotations, the description covers the critical scoping, alternative routing, and pagination behavior. It does not mention timeframe or the analytics/orchestration parameters, but those are adequately documented 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 the schema already documents every parameter including enums and required fields. The description adds some meaning around pagination with cursor and confirms the absence of a subreddit field, but largely restates enum values already present in 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 with scope: 'Search Reddit posts site-wide by keyword.' It explicitly distinguishes itself from reddit_subreddit_search_list, so an agent can route correctly 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 Guidelines5/5

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

Names the alternative tool and the exact condition that selects it ('not scoped to one subreddit — use reddit_subreddit_search_list for that'). It also clarifies that query is required and that no subreddit field exists, leaving little 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