Skip to main content
Glama
ismailsaoulaj

reddit-mcp-server

search_knowledge

Find factual Reddit threads and technical explanations using broad web search. Uncovers content Reddit's own search misses, with optional subreddit and time filters.

Instructions

STEP 1: FOUNDATION SEARCH. Use this to find factual threads or technical explanations. This uses a broad web-search (DuckDuckGo) to find Reddit threads that Reddit's own search might miss. Note: Pagination is not supported for this specific tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
subredditNo
time_filterNoall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe extracted posts.
statusNoStatus of the request (e.g., success, partial_timeout).success
messageNoSystem message or warning (especially if partial_timeout occurred).
data_sourceNoProvenance of the data: None = official Reddit API, 'arctic_shift' = community archive (metrics may lag live Reddit), 'saved_rss' = the user's private saved-items feed (scores/comment counts unavailable).
meta_contextYesTemporal and spatial context for the AI.
next_page_tokenNoPass this token to the tool again to fetch the next page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv0.3.2
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedOutput schema / properties / data / items / properties / age_in_days / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / data / items / properties / age_in_days / description
      Previous value: -"Days since post was created. 0 means posted today."New value: +"Days since post was created. None means the timestamp is unknown."
    • removedOutput schema / properties / data / items / properties / age_in_days / type
      Removed value: -"integer"
    • addedOutput schema / properties / data_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Provenance of the data: None = official Reddit API, 'arctic_shift' = community archive (metrics may lag live Reddit), 'saved_rss' = the user's private saved-items feed (scores/comment counts unavailable)."
      +}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It transparently discloses that it uses DuckDuckGo and that pagination is not supported, which helps agents understand result scoping. It does not mention rate limits or auth, but for a read-only search tool the disclosed traits are helpful.

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 tightly written in three short sentences with no filler. Each sentence adds value: purpose, mechanism, and a key limitation.

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?

The output schema and input schema cover the technical fields, and the description supplies workflow positioning and the no-pagination constraint. This is enough for an agent to select and invoke the tool effectively, though a bit more explicit sibling differentiation would make it perfect.

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

Parameters2/5

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

The schema has 0% description coverage and the description does not mention query, limit, subreddit, or time_filter by name. It only implicitly suggests that query is free-text, so the description fails to compensate for the low schema coverage.

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 clearly states the tool's role as 'STEP 1: FOUNDATION SEARCH' and its purpose: to find 'factual threads or technical explanations.' It also distinguishes itself from siblings by noting it uses a broad DuckDuckGo web search to find Reddit threads that Reddit's own search might miss.

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?

The description provides a clear when-to-use context ('STEP 1: FOUNDATION SEARCH') and explains the broad web-search approach. It mentions the no-pagination limitation, but it does not explicitly list exclusions or name alternative tools.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ismailsaoulaj/reddit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server