Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_subreddit

Retrieve recent posts from a subreddit with engagement metrics, sorting, timeframe, and pagination, so you can analyze community activity and trends.

Instructions

reddit: Subreddit Posts. GET /v1/reddit/subreddit. Provide one of: subreddit, url. Get recent posts from a subreddit with engagement metrics Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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>"
    },
    "name": "reddit_subreddit"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order
trimNoSet true for a trimmed response.
afterNoAfter to get more posts. Get 'after' from previous response.
subredditYesSubreddit name
timeframeNoTimeframe to get posts from
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the cost model in detail, including that failed and cached requests are free, which is real behavioral value. It omits permission/auth requirements, rate limiting, and what the returned posts actually contain beyond 'engagement metrics'.

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?

Front-loads identity, route, and the required input before the pricing detail, and every sentence is informative. The cost paragraph runs to three sentences and could be tightened, but nothing is filler.

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

Completeness3/5

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

For a six-parameter tool with no annotations and no output schema, the definition covers cost and pagination hints only indirectly. It should say more about the shape of returned posts and the valid values for sort and timeframe, which are free-form strings with only examples 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 coverage is 100%, so all six parameters are documented in the schema itself, giving a baseline of 3. The description adds no meaning to sort, timeframe, trim, after, or cache_max_age, and its 'Provide one of: subreddit, url' claim conflicts with a schema that marks subreddit required, exposes no url property, and sets additionalProperties=false.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Get recent posts from a subreddit with engagement metrics') plus the underlying route, which separates it from generic reddit_search siblings. It does not explicitly distinguish itself from reddit_subreddit_details or reddit_subreddit_search, so it falls short of a 5.

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

Usage Guidelines3/5

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

Gives an input-selection rule ('Provide one of: subreddit, url') and a detailed billing rule (1 credit on success; errors, blocked, timed-out, invalid, and cache hits free), which is genuinely useful decision context. However, it never says when to prefer this over reddit_subreddit_details, reddit_subreddit_search, or reddit_search.

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