Skip to main content
Glama

reddit-com

by com.jojapi

posts/search-posts

get_posts_search_posts

posts/search-posts Group: Posts. Billing per call: 1 Credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsfwNo- Whether to retrieve content that is not safe for work (e.g., 18+ content) - Default: `false` - The `true` is yes, the `false` is no
sortNo- Sort by - Default: `relevance` - Choose one of the values below - `relevance`: Relevance - `hot`: Hot - `top`: Top - `new`: New - `comments`: Comment count
timeNo- Time - Default: `all` - Choose one of the values below - `all`: All time - `year`: Past year - `month`: Past month - `week`: Past week - `day`: Today - `hour`: Past hour
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: `MjQ=`

Schema Changelog

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

  1. First observed

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits such as side effects, permissions, rate limits, or return behavior. The description only mentions billing and group, offering zero transparency about what the tool does or any consequences of invoking it. This is a significant gap for a tool that presumably performs a search.

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

Conciseness1/5

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

The description is only 8 words: 'posts/search-posts Group: Posts. Billing per call: 1 Credits.' While concise, it is under-specified to the point of being non-informative. It does not front-load any useful information for an AI agent deciding whether to use this tool. This is not conciseness but severe under-description.

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

Completeness1/5

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

With 5 parameters, no output schema, and no annotations, the description should explain the tool's purpose, typical usage, and paging behavior. The description fails to provide any of this. The schema handles parameter details, but the overall context—what the tool does, when to call it, how pagination works—is missing. The tool is completely under-specified for its complexity.

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 input schema provides descriptions for all 5 parameters (100% coverage), including defaults and enum options for sort and time, plus details on nextPage. Thus, the description does not need to add much. The schema already explains the purpose of each parameter. The description adds nothing extra, but given high schema coverage, a baseline of 3 is appropriate.

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 states 'posts/search-posts Group: Posts. Billing per call: 1 Credits.' It does not explicitly state that this tool searches posts, nor does it distinguish it from sibling tools like get_search_people or get_search_communities. The verb 'search_posts' is implied in the name, but the description provides no explicit purpose. This is clearer than a pure tautology but still vague.

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. Sibling tools like get_auto_complete, get_posts_comments, and get_search_* tools exist, but the description gives no context for selecting this specific tool. No mentions of prerequisites, exclusions, or typical use cases.

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