Skip to main content
Glama

Superpowers.social

by social.superpowers
OverviewDiscussionsAdmin

Get Subreddit Posts

reddit-get-posts
Read-onlyIdempotent

Get posts from a subreddit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results to return (default 10)
subredditYesSubreddit name without r/ prefix
text_onlyNoHeadline mode: return only {id, title} per post. Drops author, subreddit, date, URL, and the body preview. Use for a cheap first pass to pick posts worth fetching with reddit-get-post. Leave false when you need bodies, authors, or links.
time_filterNoTime filter for top sort: hour, day, week, month, year, allweek

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / sort
      Removed value: -{
-  "default": "hot",
-  "description": "Sort: hot, new, top, rising",
-  "type": "string"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / text_only / description
      Previous value: -"If true, return only id and title per post to save tokens."New value: +"Headline mode: return only {id, title} per post. Drops author, subreddit, date, URL, and the body preview. Use for a cheap first pass to pick posts worth fetching with reddit-get-post. Leave false when you need bodies, authors, or links."
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds no additional behavioral context—no mention of default sorting, time filtering, text_only mode, or response shape—so it contributes nothing beyond the structured annotations.

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 zero wasted words. It is easy to parse, but it is so terse that it essentially restates the title, which keeps it from being outstanding.

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

Completeness3/5

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

For a simple read-only listing tool with full schema coverage and safety annotations, the description is minimally adequate. It does not explain return shape or how to choose this over reddit-search, but the schema and annotations compensate for most needs, leaving it at the minimum viable level.

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?

Schema description coverage is 100%; all four parameters have meaningful descriptions, including the detailed text_only note referencing reddit-get-post. The tool description adds no parameter-level meaning, so the baseline of 3 for high coverage 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 uses a clear verb ('Get') and resource ('posts from a subreddit'), which separates it from user-specific tools like reddit-get-user-posts and from Twitter tools. However, it does not explicitly distinguish itself from reddit-get-post or reddit-search, so it doesn't fully earn a 5.

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 gives no guidance on when to use this tool versus any alternative. It does not mention reddit-search for queries, reddit-get-post for individual posts, or any exclusions. The only hint appears in the text_only parameter schema, not in the description itself.

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

All Superpowers.social 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