AIsa Reddit

subreddit

get_reddit_subreddit

Read-onlyIdempotent

Returns the post stream of one subreddit with an after token to page. Posts carry the same fields as get_reddit_search, including title, author, selftext, score, ups, upvote_ratio, num_comments, created_utc, created_at_iso, url, permalink and subreddit_subscribers. sort accepts best, hot, new, top and rising. Important: timeframe is only accepted together with sort=top, and any other combination returns 400 rather than ignoring the parameter. Subreddit names are case-sensitive. Measured at about 18 KB for 24 posts. To search inside the same subreddit use get_reddit_subreddit_search, and for its metadata use get_reddit_subreddit_details.

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

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": "get_reddit_subreddit"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order Provider reference (supplier schema): `{"enum":["best","hot","new","top","rising"],"type":"string"}`.
`trim`	No	Set to true for a trimmed down version of the response
`after`	No	After to get more posts. Get 'after' from previous response.
`subreddit`	Yes	Subreddit name
`timeframe`	No	Timeframe to get posts from. Runtime requires `sort=top` when `timeframe` is provided. Provider reference (supplier schema): `{"enum":["all","day","week","month","year"],"type":"string"}`.
`cache_max_age`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "subreddit"
+]
```

Changed5 schema fields changedOct 20, 2026

addedInput schema / properties / after / description

Added value: +"After to get more posts. Get 'after' from previous response."

addedInput schema / properties / sort / description

Added value: +"Sort order\n\nProvider reference (supplier schema): `{\"enum\":[\"best\",\"hot\",\"new\",\"top\",\"rising\"],\"type\":\"string\"}`."

addedInput schema / properties / subreddit / description
```
Added value: +"Subreddit name"
```

addedInput schema / properties / timeframe / description

Added value: +"Timeframe to get posts from. Runtime requires `sort=top` when `timeframe` is provided.\n\nProvider reference (supplier schema): `{\"enum\":[\"all\",\"day\",\"week\",\"month\",\"year\"],\"type\":\"string\"}`."

addedInput schema / properties / trim / description

Added value: +"Set to true for a trimmed down version of the response"

Changed12 schema fields changedOct 15, 2026

removedInput schema / properties / after / description

Removed value: -"After to get more posts. Get 'after' from previous response."

removedInput schema / properties / after / example
```
Removed value: -"t3_1234567890"
```
addedInput schema / properties / cache_max_age
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / sort / description
```
Removed value: -"Sort order"
```

removedInput schema / properties / sort / enum

Removed value: -[
-  "best",
-  "hot",
-  "new",
-  "top",
-  "rising"
-]

removedInput schema / properties / subreddit / description
```
Removed value: -"Subreddit name"
```

removedInput schema / properties / timeframe / description

Removed value: -"Timeframe to get posts from. Runtime requires `sort=top` when `timeframe` is provided."

removedInput schema / properties / timeframe / enum

Removed value: -[
-  "all",
-  "day",
-  "week",
-  "month",
-  "year"
-]

removedInput schema / properties / trim / description

Removed value: -"Set to true for a trimmed down version of the response"

removedInput schema / properties / trim / example
```
Removed value: -"false"
```

changedInput schema / properties / trim / type

Previous value: -"boolean"New value: +"string"

changedInput schema / required

Previous value: -[
-  "subreddit"
-]New value: +[]

Changed2 schema fields changedSep 18, 2026
- addedInput schema / properties / after / example
```
Added value: +"t3_1234567890"
```
- addedInput schema / properties / trim / example
```
Added value: +"false"
```
First observedSep 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. Beyond that, the description adds important behavioral details: the 400 error for timeframe without sort=top, case sensitivity, paging behavior, and an approximate response size of 18 KB for 24 posts.

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 purpose is front-loaded, followed by practical constraints and sibling-tool routing. The sentences are dense and purposeful, including the response-size estimate, with no redundant repetition of schema fields.

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?

The tool has an output schema, so the description need not fully document return values, yet it still gives useful context about post fields and response size. Combined with the paging and error guidance, it provides enough information to invoke the tool correctly.

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 high at 83%, so many parameter details are already structured. The description still adds useful semantics for sort values, the timeframe/sort dependency, after-token paging, and subreddit case sensitivity, though it does not explain trim or cache_max_age.

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 gives a specific verb and resource: it returns the post stream of one subreddit and supports paging via an after token. It also explicitly distinguishes this tool from get_reddit_subreddit_search and get_reddit_subreddit_details, so an agent can route correctly without opening the 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?

It states when to use this tool vs alternatives by naming get_reddit_subreddit_search for in-subreddit search and get_reddit_subreddit_details for metadata. It also gives concrete invocation constraints: timeframe requires sort=top, invalid combinations return 400, and subreddit names are case-sensitive.

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?