Skip to main content
Glama

xpay✦ Marketing Collection

scrapecreators_subreddit_search

Subreddit Search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order. For posts/media: relevance, hot, top, new, comments. For comments: relevance, top, new
queryNoSearch query to find matching content
cursorNoCursor to get more results. Get 'cursor' from previous response.
filterNoType of content to search for (default: posts). Response will only include the matching key (e.g. filter=posts returns only 'posts', not 'comments' or 'media')
subredditYesSubreddit name (e.g. 'Fitness', not 'r/Fitness' or a full URL)
timeframeNoTimeframe to filter results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.4/5.0
Behavior1/5

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

With no annotations, the description should disclose behavior, but it only states 'Subreddit Search'. It does not mention what content types are returned, pagination, search semantics, or any side effects. The agent has no idea what invoking this tool entails.

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 under-specified: a single noun phrase with no structure. While it is short, it is not concise but rather lacks necessary information, earning a score of 2.

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?

For a tool with 6 parameters and no output schema, the description is entirely inadequate. It provides no context about how to use the tool, what results to expect, or how it relates to the many sibling scraping tools.

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%, and the schema descriptions are detailed (e.g., filter, cursor). The description adds no parameter semantics beyond the schema, but the baseline of 3 applies because the schema carries the full burden.

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 'Subreddit Search' merely restates the tool's name, providing no specific verb or resource detail. It does not distinguish this tool from siblings like scrapecreators_subreddit_posts or scrapecreators_reddit, making it a tautology.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to guess based solely on the name and schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources