Skip to main content
Glama

reddit-com

by com.jojapi

search-comments

get_search_comments

search-comments 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 - `top`: Top - `new`: New
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: `MjU=`

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?

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only mentions billing credits. It does not disclose return values, pagination behavior, required authorization, or any side effects. The schema mentions nextPage from meta, but this is in structured fields, not the description.

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, but this is under-specification rather than effective conciseness. The phrase 'search-comments' is redundant with the title, and the billing note is the only additional piece of information. There is no meaningful structural content.

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?

This is a search tool with four parameters, no output schema, and no annotations. The description provides none of the context needed to understand what the tool returns, how pagination works, or how it differs from the many sibling search tools. This is far from complete.

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%, and each parameter in the input schema has a meaningful description, including defaults, examples, and enum options. The tool description itself adds no parameter information, but the baseline of 3 applies because the schema already documents the parameters well.

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

Purpose1/5

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

The description is just 'search-comments', which restates the tool's title/name and provides no verb or resource to explain what the tool does. It does not clarify the scope of the search or distinguish it from sibling tools like get_posts_comments or get_subreddit_comments.

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?

There is no usage guidance at all. The description does not mention when to use this tool versus alternatives, nor does it provide context such as typical use cases or prerequisites. This qualifies as 'no guidance'.

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