AIsa Reddit

details

get_reddit_subreddit_details

Read-onlyIdempotent

Returns metadata about one subreddit, by name or by URL: subreddit_id, display_name, subscribers, weekly_active_users, weekly_contributions, description, rules, icon_img, header_img, advertiser_category, submit_text and created_at. Use it to size a community or read its rules before posting anything elsewhere. The name is case-sensitive, so AskReddit resolves and askreddit does not. Measured at about 5 KB, the smallest response here. It returns no posts at all: for those call get_reddit_subreddit, or get_reddit_subreddit_search to query within the community.

Usage-based billing; Default request estimate: $0.00188 USD (not a fixed price). Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`url`	No	Subreddit URL
`subreddit`	No	Subreddit name. MUST be case sensitive. So 'AskReddit' not 'askreddit'.
`cache_max_age`	No	If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / cache_max_age

Added value: +{
+  "description": "If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with \"cached\": true and a \"cached_at\" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching)",
+  "enum": [
+    "14d",
+    "1d",
+    "30d",
+    "3d",
+    "7d"
+  ],
+  "type": "string"
+}

addedInput schema / properties / subreddit / description

Added value: +"Subreddit name. MUST be case sensitive. So 'AskReddit' not 'askreddit'."

addedInput schema / properties / url

Added value: +{
+  "description": "Subreddit URL",
+  "type": "string"
+}

Changed3 schema fields changedOct 15, 2026

removedInput schema / properties / subreddit / description

Removed value: -"Subreddit name. MUST be case sensitive. So 'AskReddit' not 'askreddit'."

removedInput schema / properties / subreddit / example
```
Removed value: -"AskReddit"
```

removedInput schema / properties / url

Removed value: -{
-  "description": "Subreddit URL",
-  "example": "https://www.reddit.com/r/AbsoluteUnits/",
-  "type": "string"
-}

Changed2 schema fields changedSep 18, 2026
- addedInput schema / properties / subreddit / example
```
Added value: +"AskReddit"
```
- addedInput schema / properties / url / example
```
Added value: +"https://www.reddit.com/r/AbsoluteUnits/"
```
First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: approximate response size (~5 KB, smallest response here), the case-sensitivity gotcha, and the explicit scope exclusion (returns no posts). It doesn't discuss caching semantics, though the schema covers those.

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?

Front-loaded with the core purpose and return fields, then usage, then the case-sensitivity caveat, then sibling routing. Every sentence carries information; the trailing billing block is platform metadata rather than authored prose.

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

Completeness5/5

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

An output schema exists so return-value documentation is not required, and the annotations already carry the safety profile. The description nonetheless covers identity, scope, size, naming constraint, and sibling routing, which is everything an agent needs to select and invoke this tool correctly.

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 baseline is 3. The description adds only the framing that the target can be given 'by name or by URL' (clarifying that the two params are alternatives) and restates the case-sensitivity rule already documented on the subreddit field. The cache_max_age enum is left to 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 ('returns metadata about one subreddit') and enumerates the exact fields returned, so the agent knows precisely what it gets. It also explicitly distinguishes itself from siblings by noting it returns no posts and naming get_reddit_subreddit and get_reddit_subreddit_search as alternatives.

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?

Gives explicit when-to-use guidance ('size a community or read its rules before posting anything elsewhere') and explicit when-not-to-use routing ('It returns no posts at all: for those call get_reddit_subreddit, or get_reddit_subreddit_search'). Alternatives are named with the condition that selects them.

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

All AIsa Reddit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?