Skip to main content
Glama

glim.sh

by sh.glim
OverviewDiscussionsAdmin

Reddit Get

glim_reddit_get
Read-onlyIdempotent

Fetch a Reddit post, subreddit, or user by ref. Posts return comments; subreddits and users return profile metadata plus recent activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesPost ID or URL, subreddit ref (r/programming or reddit.com/r/programming), or user ref (u/spez or reddit.com/user/spez)
sortNoListing post sorthot
timeNoListing time rangeday
limitNoMax subreddit posts (1-10), each with full content + top comments
cursorNoPagination cursor from a prior subreddit response's next_cursor
formatNoOutput format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing.text
comment_sortNoComment sort. Post refs only: subreddit/user listings always hydrate a fixed 2 top-level comments sorted by top.confidence
comment_depthNoMax nesting depth (post refs only)
comment_limitNoMax comments (post refs only)
include_postsNoInclude recent posts for user refs
include_commentsNoInclude recent comments for user refs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / comment_depth / description
      Previous value: -"Max nesting depth"New value: +"Max nesting depth (post refs only)"
    • changedInput schema / properties / comment_limit / description
      Previous value: -"Max comments"New value: +"Max comments (post refs only)"
    • changedInput schema / properties / comment_sort / description
      Previous value: -"Comment sort"New value: +"Comment sort. Post refs only: subreddit/user listings always hydrate a fixed 2 top-level comments sorted by top."
    • addedInput schema / properties / cursor / maxLength
      Added value: +64
    • addedInput schema / properties / cursor / pattern
      Added value: +"^\\s*(?:[tT]\\d_)?[a-zA-Z0-9]+\\s*$"
  2. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Pagination cursor from a prior subreddit response's next_cursor",
+  "type": "string"
+}
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max listing items"New value: +"Max subreddit posts (1-10), each with full content + top comments"
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +10
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare read-only, idempotent, non-destructive, so safety is clear. The description adds that posts return comments and subreddits/users return profile plus recent activity, but lacks specifics like subreddit listing behavior (sort, limit, pagination) or user activity scope. Adds some context beyond annotations.

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?

The description is a single sentence that efficiently covers three entity types and their return behavior. No filler or unnecessary words; every part adds value.

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?

Given 11 parameters and no output schema, the description covers high-level behavior but omits details on subreddit/user responses (e.g., they include listings with sort/limit parameters) and pagination. Adequate for a basic understanding but incomplete for full context.

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%, so the baseline is 3. The description does not elaborate on parameters beyond the schema; it only mentions return behavior for different ref types. No additional parameter meaning is provided.

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?

The description clearly specifies the verb 'Fetch' and the resource: Reddit post, subreddit, or user by ref. It distinguishes behavior among entity types: posts return comments, subreddits and users return profile metadata plus recent activity. This differentiates from sibling tools like glim_reddit_search.

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

Usage Guidelines3/5

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

The description implies usage when a ref is available but does not explicitly state when to use this tool versus alternatives like search. No when-not-to-use or exclusion criteria are provided, leaving the agent to infer context.

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

All glim.sh 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