Skip to main content
Glama

AIsa Reddit

by one.aisa
OverviewDiscussionsAdmin

search

get_reddit_subreddit_search
Read-onlyIdempotent

Searches inside one subreddit and returns matching posts with a cursor token to page. Posts carry title, author, selftext, score, ups, upvote_ratio, num_comments, created_utc, created_at_iso, url, permalink and is_video. Despite what sort suggests, every sort value returns posts and only posts: comments and media were confirmed absent from all five. Measured at about 5 KB and 2 seconds, faster than get_reddit_search, which searches all of Reddit and pages with after instead of cursor. For the replies under a result, pass its url to 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.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order. For posts/media: relevance, hot, top, new, comments. For comments: relevance, top, new Provider reference (supplier schema): `{"enum":["relevance","hot","top","new","comments"],"type":"string"}`.
queryNoSearch query to find matching content
cursorNoCursor to get more results. Get 'cursor' from previous response.
subredditNoSubreddit name (e.g. 'Fitness', not 'r/Fitness' or a full URL)
timeframeNoTimeframe to filter results Provider reference (supplier schema): `{"enum":["all","year","month","week","day","hour"],"type":"string"}`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Cursor to get more results. Get 'cursor' from previous response.",
+  "type": "string"
+}
    • addedInput schema / properties / query / description
      Added value: +"Search query to find matching content"
    • addedInput schema / properties / sort / description
      Added value: +"Sort order. For posts/media: relevance, hot, top, new, comments. For comments: relevance, top, new\n\nProvider reference (supplier schema): `{\"enum\":[\"relevance\",\"hot\",\"top\",\"new\",\"comments\"],\"type\":\"string\"}`."
    • addedInput schema / properties / subreddit / description
      Added value: +"Subreddit name (e.g. 'Fitness', not 'r/Fitness' or a full URL)"
    • addedInput schema / properties / timeframe / description
      Added value: +"Timeframe to filter results\n\nProvider reference (supplier schema): `{\"enum\":[\"all\",\"year\",\"month\",\"week\",\"day\",\"hour\"],\"type\":\"string\"}`."
  2. Changed9 schema fields changed
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Cursor to get more results. Get 'cursor' from previous response.",
-  "example": "eyJjYW5kaWRhdGVzX3JldHVybmVkIjoi...",
-  "type": "string"
-}
    • removedInput schema / properties / query / description
      Removed value: -"Search query to find matching content"
    • removedInput schema / properties / query / example
      Removed value: -"push ups"
    • removedInput schema / properties / sort / description
      Removed value: -"Sort order. For posts/media: relevance, hot, top, new, comments. For comments: relevance, top, new"
    • removedInput schema / properties / sort / enum
      Removed value: -[
-  "relevance",
-  "hot",
-  "top",
-  "new",
-  "comments"
-]
    • removedInput schema / properties / subreddit / description
      Removed value: -"Subreddit name (e.g. 'Fitness', not 'r/Fitness' or a full URL)"
    • removedInput schema / properties / timeframe / description
      Removed value: -"Timeframe to filter results"
    • removedInput schema / properties / timeframe / enum
      Removed value: -[
-  "all",
-  "year",
-  "month",
-  "week",
-  "day",
-  "hour"
-]
    • changedInput schema / required
      Previous value: -[
-  "subreddit"
-]New value: +[]
  3. Changed2 schema fields changed
    • addedInput schema / properties / cursor / example
      Added value: +"eyJjYW5kaWRhdGVzX3JldHVybmVkIjoi..."
    • addedInput schema / properties / query / example
      Added value: +"push ups"
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this a read-only, idempotent, open-world, non-destructive call, so the safety profile is covered. The description goes well beyond that with measured cost/latency (~5 KB, ~2 seconds), the pagination model (cursor token, contrasted with get_reddit_search's 'after'), and the empirical constraint that only posts are ever returned. That is exactly the kind of operational context annotations cannot express.

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?

Purpose and scope are front-loaded, and the comparison sentences each carry distinct routing value. It is a dense single paragraph, and the enumeration of return fields duplicates what the output schema already provides, which is the one clearly removable element (ignoring the injected pricing boilerplate).

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?

For a five-parameter, zero-required search tool with an output schema present, the description supplies everything needed to call it correctly: scope, pagination, alternatives, latency/cost expectations, and the sort caveat. Nothing important is deferred to inference.

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 the baseline is 3. The description earns an extra point by resolving a genuine ambiguity: the supplier enum advertises a 'comments' sort value that the description reports as never producing comments, which the schema alone would mislead an agent about. Cursor usage is also clarified in prose; subreddit name format and timeframe are 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 with explicit scope: 'Searches inside one subreddit and returns matching posts with a cursor token to page.' It immediately distinguishes itself from the sibling get_reddit_search by contrast (one subreddit vs all of Reddit, cursor vs after), so an agent can route without opening either 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 two alternatives explicitly and the condition selecting each: get_reddit_search for site-wide search, and get_reddit_post_comments ('pass its url') for retrieving replies under a result. It also warns that the sort parameter should not be read as implying comment/media results, which preempts a likely misuse. This is close to a complete routing guide.

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

All AIsa Reddit toolsInspect
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