Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_posts

Search Reddit posts by keyword across all subreddits or within a specific community to find discussions and content on any topic.

Instructions

Full-text search across Reddit or within a specific subreddit

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": "search_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
afterNo
limitNo
queryYes
subredditNo
time_filterNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't mention that this is a read-only operation, that it returns a list, anything about pagination behavior, rate limits, or sorting defaults beyond what's in the schema. The description is minimal for a search tool.

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?

The description is a single, front-loaded sentence with no waste. It is effectively concise for what it does, but being too short contributes to the other gaps.

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

Completeness2/5

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

For a six-parameter search tool with no output schema and no annotations, the description is far too sparse. It fails to cover authentication needs, response format, or any parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only vaguely implies a query and an optional subreddit scope, but does not explain sort, after, limit, or time_filter parameters at all. This leaves six parameters essentially undocumented.

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?

States a specific verb (search) and resource (posts) with scope (full-text, across Reddit or within a subreddit). This is clear, but it doesn't distinguish itself from sibling tools like get_subreddit_posts, which also retrieve posts.

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 only offers the scope ('or within a specific subreddit') with no when-to-use guidance or alternatives. It doesn't say when to use search_posts versus get_subreddit_posts or get_post_detail.

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

Deploy Server

Other Tools