Skip to main content
Glama

glim.sh

by sh.glim
OverviewDiscussionsAdmin

Reddit Search

glim_reddit_search
Read-onlyIdempotent

Search Reddit posts. Each result comes with full post content and its top comments, so a single search usually answers the question without follow-up. Compact human-readable text by default; pass format='json' for full structured data. Use glim_reddit_get(ref) for a single post's complete comment tree. Page with cursor (response gives next_cursor when more exist). See docs://reddit-search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. Keep 'relevance' (default) for question or topic queries - it ranks by how well posts match your query. 'top'/'hot' rank by score/recency and largely ignore the query text, so use them only to browse what's popular in a subreddit.relevance
timeNoTime rangeall
limitNoMax posts (1-10), each with full content + top comments
queryYesSearch query (e.g. 'subreddit:programming machine learning')
cursorNoPagination cursor from a prior response's next_cursor
formatNoOutput format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.text
end_dateNoOnly posts before this date (YYYY-MM-DD)
start_dateNoOnly posts on or after this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / maxLength
      Added value: +64
    • addedInput schema / properties / cursor / pattern
      Added value: +"^\\s*(?:[tT]\\d_)?[a-zA-Z0-9]+\\s*$"
  2. Changed4 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"Pagination cursor from a prior response's next_cursor"
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max posts"New value: +"Max posts (1-10), each with full content + top comments"
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +10
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context: results include top comments, default textual output, optional JSON format, and pagination via cursor. No contradictions.

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?

Four concise, front-loaded sentences. Each sentence adds distinct value: main purpose, output format options, sibling tool reference, and pagination with docs link. No fluff.

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 search tool with 8 parameters and no output schema, the description sufficiently covers result content, output formats, pagination, and refers to docs for details. It also maps to sibling tools.

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 provides full parameter descriptions (100% coverage). The description adds value by reinforcing default format 'text', explaining the cursor parameter usage, and noting that passing format='json' yields structured data.

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 clearly states the tool searches Reddit posts and specifies that results include full post content and top comments. It distinguishes from the sibling tool glim_reddit_get, which is for a single post's comment tree.

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 advises using glim_reddit_get for deeper comment tree needs and implies that a single search often suffices. However, it does not explicitly state when not to use this tool.

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

All glim.sh 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