AIsa Social

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.

Input Schema

TableJSON 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`	No	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

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already establish the read-only, idempotent, non-destructive profile, so the description is free to add runtime behavior instead. It does: the timeframe/sort=top 400 error (rather than silent ignoring), case-sensitive subreddit names, pagination via the after token, and a concrete ~18 KB / 24 posts size figure. Auth and rate-limit behavior are still unstated, so it falls 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.

Conciseness4/5

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

Front-loaded with the core purpose and scope, then constraints, then routing. Every sentence carries information, including the size estimate and error edge case. The appended pricing boilerplate adds length without helping tool selection.

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?

For a 6-param, unpaginated-boundary tool with an output schema, this covers purpose, constraints, paging, alternatives and approximate payload size. Minor gaps remain: the trim payload reduction and cache_max_age are not clarified in narrative form. Nothing an agent needs to call it successfully is missing.

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 83%, so the schema already documents sort, timeframe, after and trim; the description largely restates the sort enum and the timeframe constraint. It adds the genuinely useful case-sensitivity note for subreddit, but leaves cache_max_age and the semantics of trim (what gets removed) unexplained. Baseline 3 is appropriate when the schema carries most of the load.

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+resource and scope: the post stream of one subreddit. It explicitly distinguishes itself from the three nearest siblings (get_reddit_search, get_reddit_subreddit_search, get_reddit_subreddit_details), so an agent can route correctly without opening any 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?

Names the alternatives and the exact conditions that select them: use get_reddit_subreddit_search to search inside the same subreddit, get_reddit_subreddit_details for its metadata. It also states the sort=top pairing rule for timeframe, giving explicit when-to-use behavior rather than leaving it to inference.

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

All AIsa Social 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?