Skip to main content
Glama

search_posts

Read-onlyIdempotent

Search Reddit posts by keywords, subreddit, author, and date range; sort results and choose live or archive sources for targeted research.

Instructions

Search posts by keywords, subreddit, author and date range.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault: relevance on live, new on archive. relevance/hot/top/comments need live; new works on both; old only on the archive.
timeNoTime window
afterNoArchive only: posted after this date (2024-01-31, epoch, or '30d')
limitNo
queryNoKeywords. Live supports reddit search syntax.
authorNoRestrict to one author
beforeNoArchive only: posted before this date
cursorNonext_cursor from a previous call
sourceNoData source. 'auto' tries live reddit.com (if a session cookie is configured) and falls back to the Arctic Shift archive; 'live' or 'archive' forces one.auto
subredditNoRestrict to one subreddit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations provide strong behavioral transparency (readOnly, idempotent). The description adds no novel behavioral context—such as handling of pagination or source constraints—that is not already captured in the extensive input schema.

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 highly concise, using a single sentence to list the tool's primary function and its main filtering dimensions without any unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity of the schema, which includes 10 parameters for sorting, pagination (cursor), time windows, and live vs archive sources, the description is grossly incomplete. It only mentions four general search categories, ignoring the depth of the search functionality.

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?

The schema coverage is high at 90%, setting a baseline of 3. The description reiterates the four main criteria (keywords, subreddit, author, date range), which helps confirm the scope of the parameters, though it adds no specific semantic meaning beyond the schema's detailed descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Search') and resource ('posts'), and lists the primary filtering mechanisms. However, it does not explicitly differentiate this search function from sibling tools like 'get_post' or 'browse_subreddit'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives; it is a general list of capabilities. There are no exclusions or use-case recommendations provided.

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