Skip to main content
Glama
Sign In

Weir: Reddit and X (Twitter) data

by io.weirapp
OverviewDiscussionsAdmin

List a community's posts: hot, new, rising, top, or controversial

get_subreddit_posts
Read-onlyIdempotent

List a community's posts: hot, new, rising, top, or controversial. A community's own listing, with no keyword: everything new in r/saas, or this week's top posts in r/startups. Use this rather than search when the community is the filter — Reddit's search needs a query and cannot express "everything".

name also takes popular, all, or several communities joined with +, which reads them as one listing in a single call (and is billed as one request).

Pages are newest-cursor-forward and stop at about 1,000 posts, Reddit's own ceiling, where nextCursor becomes null. NSFW posts are left out unless includeNsfw=true; how many were left out is in meta.omittedNsfw. A community that does not exist, or is private, banned, or quarantined, is a 404 whose details.reason says which. Costs 1 credit + 3 credits per post returned. When meta.nextCursor is set, call again with cursor set to it for the next page.

Input Schema

NameRequiredDescriptionDefault
geoNoRegion for `popular` sorted by `hot` only: a country code (`DE`), a US state (`US_CA`), or `GLOBAL`.
nameYesA community name without `r/`; `popular` or `all` for the site-wide listings; or up to 25 communities joined with `+` (`saas+startups+entrepreneur`) to read them as one listing in a single call.
sortNoReddit's own orderings. `new` is arrival order, which is what watching a community needs; `hot` is Reddit's default front page.hot
timeNoWindow for `top` and `controversial` only. Defaults to `day` for those sorts.
limitNoPosts per page, before the NSFW rule is applied.
cursorNo`meta.nextCursor` from the previous page, unchanged. Opaque, signed, and bound to the other parameters: change any of them and start again without a cursor.
includeNsfwNoInclude posts marked NSFW. Off by default; what it removes is reported in `meta.omittedNsfw`, so a short or empty page is never mistaken for a quiet one.false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: discloses the ~1,000-post pagination ceiling where `nextCursor` becomes null, the NSFW exclusion rule and its `meta.omittedNsfw` accounting, the 404 with `details.reason` for missing/private/banned/quarantined communities, and the exact cost model (1 credit + 3 per post). Idempotency and read-only status are already in annotations, so this is pure added value.

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?

Front-loaded with purpose and the sibling comparison, then organized into cost/pagination/NSFW/error paragraphs. Dense but every sentence carries operational information an agent needs; nothing is filler.

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?

With no output schema, the description carries the return contract itself — it explains `meta.nextCursor`, `meta.omittedNsfw`, `details.reason`, and the pagination loop. For a 7-parameter listing tool with open-world scope, nothing an agent needs to call it correctly is missing.

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; the description still adds real meaning — that `name` accepts `popular`/`all`/`+`-joined communities and that a joined read is billed as one request, plus the sort/time interaction and the cursor's binding to the other parameters. It stops short of restating every field's constraints, which the schema already handles.

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?

States a specific verb+resource ('List a community's posts') plus the five orderings, and immediately distinguishes itself from search_subreddit/search_reddit by explaining that search needs a keyword and cannot express 'everything'. An agent can pick it apart from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing rule: 'Use this rather than search when the community is the filter — Reddit's search needs a query and cannot express "everything".' It also names the concrete scenarios (everything new in r/saas, this week's top in r/startups) and explains when to use the multi-community `+` form instead of multiple calls.

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

All Weir: Reddit and X (Twitter) data 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