Skip to main content
Glama
Sign In
threadr-mcp

threadr-mcp

by msaeedsakib
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_subreddit_posts

Fetch posts from any subreddit with sort options like hot, new, top, rising, or controversial to browse Reddit content by relevance or time.

Instructions

Get posts from a subreddit with sort options (hot, new, top, rising, controversial)

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": {
      "subreddit": "<subreddit>"
    },
    "name": "get_subreddit_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNohot
afterNo
limitNo
subredditYes
time_filterNoday

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 behavioral burden. It does not disclose auth requirements, rate limits, pagination behavior via 'after', return shape, or whether this is strictly read-only beyond the weak implication from 'Get'.

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 filler. It is appropriately concise, though its brevity contributes to the missing parameter and behavioral context elsewhere.

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 listing tool with five parameters, pagination, a time filter, no output schema, and no annotations, the description is too incomplete. It gives only the sort options and omits how to page, limit, or use time_filter.

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%, and five parameters are present. The description only repeats the sort enum values already listed in the schema; it adds no meaning for subreddit, after, limit, or time_filter, including when time_filter applies.

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 states a specific verb and resource: get posts from a subreddit. It also names the available sort options, so the core action is clear. However, it does not explicitly distinguish this tool from siblings like search_posts or get_user_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?

There is no guidance on when to use this tool versus alternatives such as search_posts or get_user_posts. It also does not state when not to use it or any prerequisites/context for selecting a subreddit feed.

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