Skip to main content
Glama

reddit-com

by com.jojapi

subreddit/search

get_subreddit_search

subreddit/search Group: Subreddit. Billing per call: 1 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo- Sort by - Default: `top` - Choose one of the values below - `hot`: Hot - `new`: New - `top`: Top - `controversial`: Controversial - `rising`: Rising
timeNo- Time - Default: `all` - Choose one of the values below - `all`: All time - `hour`: Past hour - `day`: Past 24 hours - `week`: Past week - `month`: Past month - `year`: Past year
queryNo- Required: true - Ex: `gaming`
nextPageNo- The page index, for paging purpose - Leave it blank for the first time - The `nextPage` can be retrieved from response of this endpoint(meta->nextPage) - Ex: `dDNfZXJ4dXdt`

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2/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 burden of disclosing behavior. It only mentions billing per call, which is a minor operational detail. It does not clarify what the search returns, whether it requires authentication, rate limits, or any side effects. Given no annotations, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short ('subreddit/search Group: Subreddit. Billing per call: 1 Credits.'), but this is under-specification, not conciseness. It omits essential purpose and usage information. There is no useful structure or front-loading of key details.

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?

With no output schema, no annotations, and a non-trivial 4-parameter tool with pagination, the description is incomplete. The schema handles parameters well, but the tool's purpose and return format are undocumented, making it difficult for an agent to understand what the tool accomplishes.

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?

The schema already covers 100% of parameter descriptions, including defaults, enums, examples, and paging via nextPage. The description adds nothing beyond that. Per the baseline for high schema coverage, this scores a 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only repeats the tool name and a generic billing note: 'subreddit/search Group: Subreddit. Billing per call: 1 Credits.' It does not state what the tool does (e.g., search within a subreddit) and does not differentiate from sibling search tools like get_search_posts or get_subreddit_comments. This is effectively a tautology of the name/title.

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

Usage Guidelines1/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. The sibling tools include multiple search variants, but the description provides no context about the tool's scope (e.g., searching within a subreddit) or when it should be preferred. This is misleading because the name suggests subreddit search, but no details support that.

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

All reddit-com toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.2/5.0
Disambiguation3/5

Several tools are easily confused: get_posts_comments, get_subreddit_comments, and get_search_comments all involve comments but target different scopes; similarly, get_subreddit_search, get_posts_search_posts, and get_search_* tools overlap in search functionality. Without detailed descriptions, an agent might select the wrong endpoint for a given intent.

Naming Consistency3/5

All tools start with 'get_', providing a consistent verb prefix. However, the structure after the prefix varies: some use entity-first (get_subreddit_comments), some action-first (get_search_comments), and one is awkward (get_posts_search_posts). This mixed pattern reduces predictability.

Tool Count5/5

Ten tools is a reasonable and well-scoped number for a Reddit read-only API server. It covers search across multiple entities and basic content retrieval without feeling bloated or too sparse.

Completeness3/5

The tool surface is heavily read-focused, covering search and content fetch, but omits many core Reddit operations such as creating posts, commenting, voting, or retrieving user profiles and subreddit details. Some endpoints like get_subreddit_awarding_totals seem niche, while more common ones (e.g., get_subreddit_info) are absent.

Resources