Skip to main content
Glama
Sign In

Desearch

by io.github.Desearch-ai
OverviewDiscussionsAdmin

Reddit

reddit
Read-only

Read public Reddit data with Desearch. Set action and that action's arguments. search (query; optional sort, timeframe, cursor): posts across all subreddits that match a keyword. subreddit (name): a subreddit's description, rules, and weekly activity; the name is case-sensitive ('AskReddit', not 'askreddit'). subreddit_posts (name; optional sort, timeframe, cursor): its posts. post (id): one post by ID or URL, without comments. comments (post_id; optional cursor): a post's comments as a tree, with the replies Reddit loaded alongside them. A post id from search or subreddit_posts can be passed to post or comments. subreddit and post return the item itself. List actions return { results, next_cursor, next }. For the next page, call again with the same action and target and cursor set to next_cursor, unchanged; next_cursor is null on the last page. A cursor lasts 24 hours.

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": {
      "action": "<action>"
    },
    "name": "reddit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNopost: Reddit post ID (example: '1q6pxwn', with or without t3_) or its full URL.
nameNosubreddit, subreddit_posts: subreddit name, case-sensitive, example: 'AskReddit'. A leading r/ is removed.
sortNosearch: 'relevance', 'new', 'top', or 'comment_count'. subreddit_posts: 'best', 'hot', 'new', 'top', or 'rising'.
queryNosearch: keyword or phrase, example: 'bittensor'.
actionYesWhat to read: 'search', 'subreddit', 'subreddit_posts', 'post', or 'comments'.
cursorNonext_cursor from the previous page of the same action and target, sent back unchanged. Omit it for the first page.
post_idNocomments: Reddit post ID (with or without t3_) or its full URL.
timeframeNosearch: only posts from this window. subreddit_posts: the window for sort 'top' (ignored with another sort; without a sort it means top).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavior beyond the readOnly/openWorld annotations: return shapes for item versus list actions, cursor pagination rules, cursor lifetime, and the difference between post data and comments as a tree. These details tell the agent how the tool behaves operationally.

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 description is dense but front-loaded: it states the tool's purpose, then organizes action descriptions in a compact list-like flow. Given five actions and eight parameters, every sentence contributes useful selection or pagination information.

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 multi-action read-only tool with no output schema, the description covers action selection, parameter targeting, pagination, return shape, and cursor lifetime. An agent can call the tool correctly without needing additional context.

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, but the description adds value by mapping parameters to actions, noting that IDs from search or subreddit_posts can feed post or comments, and explaining cursor reuse across pages. Some of this overlaps the schema, keeping it below a 5.

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 states a specific verb and resource: read public Reddit data. It then enumerates the five supported actions and what each retrieves, which makes the tool's scope clear and separates it from non-Reddit siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains how to choose among the internal actions by describing what each action returns, such as search-by-keyword versus subreddit_posts for a specific subreddit. It does not explicitly compare this tool with sibling tools like web-search or x-search, but the Reddit-specific context is clear.

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

All Desearch 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