AIsa Reddit

search

get_reddit_search

Read-onlyIdempotent

Searches every public subreddit for posts matching a query and returns posts plus an after token to page. Each post carries title, author, selftext, selftext_html, subreddit, score, ups, downs, upvote_ratio, num_comments, created_utc, created_at_iso, url, permalink, subreddit_subscribers, is_video, over_18 and spoiler. sort accepts relevance, new, top and comment_count, and timeframe narrows the window. Measured at 8 to 16 seconds and 8 to 26 KB, the slowest endpoint here. To stay inside one community use get_reddit_subreddit_search, which is faster and pages with cursor rather than after; to read one post's discussion use get_reddit_post_comments.

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": {
      "query": "<query>"
    },
    "name": "get_reddit_search"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort by Provider reference (supplier schema): `{"enum":["relevance","new","top","comment_count"],"type":"string"}`.
`time`	No
`trim`	No	Set to true for a trimmed down version of the response
`after`	No	Used to paginate to next page
`count`	No
`limit`	No
`query`	Yes	Search query
`filter`	No	Search posts or comments
`trimmed`	No
`timeframe`	No	Timeframe Provider reference (supplier schema): `{"enum":["all","day","week","month","year"],"type":"string"}`.

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: +[
+  "query"
+]
```

Changed6 schema fields changedOct 20, 2026

addedInput schema / properties / after

Added value: +{
+  "description": "Used to paginate to next page",
+  "type": "string"
+}

addedInput schema / properties / filter

Added value: +{
+  "description": "Search posts or comments",
+  "enum": [
+    "comments",
+    "posts"
+  ],
+  "type": "string"
+}

addedInput schema / properties / query / description
```
Added value: +"Search query"
```

addedInput schema / properties / sort / description

Added value: +"Sort by\n\nProvider reference (supplier schema): `{\"enum\":[\"relevance\",\"new\",\"top\",\"comment_count\"],\"type\":\"string\"}`."

addedInput schema / properties / timeframe / description

Added value: +"Timeframe\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"

Changed16 schema fields changedOct 15, 2026

removedInput schema / properties / after

Removed value: -{
-  "description": "Used to paginate to next page",
-  "example": "t3_1i8z28z",
-  "type": "string"
-}

addedInput schema / properties / count
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / limit
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / query / description
```
Removed value: -"Search query"
```
removedInput schema / properties / sort / description
```
Removed value: -"Sort by"
```

removedInput schema / properties / sort / enum

Removed value: -[
-  "relevance",
-  "new",
-  "top",
-  "comment_count"
-]

removedInput schema / properties / sort / example
```
Removed value: -"relevance"
```
addedInput schema / properties / time
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / timeframe / description
```
Removed value: -"Timeframe"
```

removedInput schema / properties / timeframe / enum

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

removedInput schema / properties / timeframe / example
```
Removed value: -"all"
```

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"

addedInput schema / properties / trimmed
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

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

Changed4 schema fields changedSep 18, 2026
- addedInput schema / properties / after / example
```
Added value: +"t3_1i8z28z"
```
- addedInput schema / properties / sort / example
```
Added value: +"relevance"
```
- addedInput schema / properties / timeframe / example
```
Added value: +"all"
```
- addedInput schema / properties / trim / example
```
Added value: +"false"
```
First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing latency (8–16 s), payload size (8–26 KB), pagination via an after token, the field list returned per post, and the accepted sort values. This is exactly the operational context an agent needs to plan a slow, wide call.

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 purpose, then performance, then routing. The long enumeration of returned fields is somewhat expendable, but every sentence carries usable information and there is no filler.

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?

The gold-standard routing and performance details make this callable with confidence, and an output schema exists so return values needn't be spelled out (the field list is mild duplication). The only real incompleteness is the unmentioned secondary parameters like filter and limit.

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?

With 60% schema coverage the schema does most of the work, and the description adds real meaning for sort and timeframe. However it says nothing about filter (posts vs comments), limit, count, trim/trimmed, or the ambiguity between 'time' and 'timeframe' — a notable gap given several near-duplicate parameters.

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?

Opening sentence gives a specific verb+resource+scope: 'Searches every public subreddit for posts matching a query'. It explicitly contrasts with two named siblings (get_reddit_subreddit_search, get_reddit_post_comments), so an agent can distinguish it without reading 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?

Provides explicit routing rules: use get_reddit_subreddit_search to stay inside one community, and get_reddit_post_comments to read one post's discussion. The alternative conditions are stated directly rather than left 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 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?