Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

reddit_subreddit_details

Fetch details for a subreddit using its name or URL, including weekly activity metrics when subscriber counts are unavailable.

Instructions

reddit: Subreddit Details. GET /v1/reddit/subreddit/details. Provide one of: subreddit, url. Get details about a subreddit. Pass a subreddit name or URL to the subreddit. Subscriber counts are not available; weekly activity counts are different 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reddit_subreddit_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSubreddit URL
subredditNoCase-sensitive subreddit name, e.g. AskReddit, not askreddit.
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

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does unusually well on cost semantics: 1 credit on success, free for errors, blocked, timed-out, invalid requests and cache hits, with not-found charged per published cost. It also warns that subscriber counts are unavailable and weekly activity is a different metric. It does not describe the response shape or rate limits, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the pricing sentences are informative, but the definition is padded: the 'GET /v1/reddit/subreddit/details' route restates internal plumbing, and 'Pass a subreddit name or URL to the subreddit' largely duplicates the preceding 'Provide one of' sentence. The trailing cost sentence is long for the value it adds after the first clause.

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 three-parameter read tool with no output schema and no annotations, the description covers cost and one-of input selection but leaves the agent guessing about returned fields and about what distinguishes this endpoint from reddit_subreddit. The complexity is modest, so the gap is real but not severe.

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 coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema: with zero required parameters, it tells the agent that exactly one of subreddit or url must be supplied. It says nothing extra about cache_max_age beyond what the schema already explains.

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?

The description states a specific verb and resource ('Get details about a subreddit') and names the two input forms accepted. It is clear what the tool returns at a high level, though it never distinguishes itself from the similarly named sibling reddit_subreddit, leaving the agent to infer that one is details and the other is likely posts or a profile.

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?

'Provide one of: subreddit, url' and 'Pass a subreddit name or URL to the subreddit' give the invocation constraint, and the note that subscriber counts are unavailable implies what the tool is not for. However, there is no explicit statement of when to choose this over reddit_subreddit or reddit_subreddit_search, so usage is only implied.

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