Skip to main content
Glama

agdata

by dev.shveik
OverviewDiscussionsAdmin

Reddit posts by subreddit, user, search

reddit
Read-only

Search Reddit or read a subreddit. Use mode hashtag with a subreddit name (no r/), profile with a username, or search with keywords, plus limit 1-20. Every record is a post with kind, id, url, title, body, author, subreddit, upvotes, comments_count, created_at, members and source; at most limit posts come back. Comments, profile and subreddit records are not returned. upvotes and comments_count can be null. Send raw true for the full original records.

Input Schema

NameRequiredDescriptionDefault
rawNotrue returns the provider's own records instead of the compact shape
modeYesprofile=user's posts, hashtag=subreddit's posts, search=keyword→posts
limitNonumber of posts wanted, 1 to 20 (default 5). A larger value is lowered to 20 and 0 or a negative one means the default; the quote follows the value used.
queryYesusername (profile), subreddit without r/ (hashtag), or search keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / raw
      Added value: +{
+  "default": false,
+  "description": "true returns the provider's own records instead of the compact shape",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld, non-idempotent), and the description adds substantial context beyond them: the exact record shape, that at most 'limit' posts come back, that comments/profile/subreddit records are excluded, that upvotes and comments_count may be null, and the effect of raw=true.

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?

One dense paragraph that is front-loaded with the action and mode usage before moving to return shape and caveats. Every sentence carries information (modes, record fields, exclusions, nullability, raw), though it is a long run-on rather than clearly segmented.

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 compensates by enumerating returned fields (kind, id, url, title, body, author, subreddit, upvotes, comments_count, created_at, members, source) and noting nullability. Combined with annotations covering safety, an agent has everything needed to call it correctly.

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 coverage is 100%, so the schema already documents mode, query, limit, and raw. The description repeats mode usage and 'no r/' and 'limit 1-20' but adds no semantics beyond the schema, so the baseline 3 applies.

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 specific verbs (search, read) and resources (Reddit posts, subreddit) and the title reinforces scope ('Reddit posts by subreddit, user, search'). The description also clarifies what the tool does NOT return (comments, profile, subreddit records), making its boundary unambiguous despite sibling tools on other platforms.

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

Usage Guidelines4/5

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

Gives per-mode usage: 'hashtag with a subreddit name (no r/), profile with a username, or search with keywords, plus limit 1-20.' This tells the agent how to trigger each path. There is no competing Reddit sibling to route to, so no explicit alternative-routing is needed, but no exclusions beyond the record-type note.

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

All agdata toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources