scrapecreators_reddit
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Subreddit URL | |
| subreddit | No | Subreddit name. MUST be case sensitive. So 'AskReddit' not 'askreddit'. |
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Subreddit URL | |
| subreddit | No | Subreddit name. MUST be case sensitive. So 'AskReddit' not 'askreddit'. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. 'Reddit' provides zero insight into whether this is a read-only operation, what data is returned, rate limits, or authentication requirements. The agent has no way to know what side effects or constraints exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One word is extremely brief, but this is under-specification rather than conciseness. The description fails to communicate any meaningful information, so the brevity is not a positive attribute.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 2 parameters that have schema descriptions, the tool description still must explain its purpose and behavior. It does not. For a scraping tool among many similar ones, this is completely inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters ('Subreddit URL', 'Subreddit name. MUST be case sensitive'), so coverage is 100%. Per rubric, baseline is 3. However, the description itself adds no parameter context beyond the schema—it does not explain how to select or combine the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is just the word 'Reddit,' which is a noun and not a verb. It does not state what the tool does (e.g., scrape posts, get subreddit info). It merely restates the platform in the tool name, failing to specify an action or resource. Sibling tools like 'scrapecreators_subreddit_posts' and 'scrapecreators_comments' indicate more specific operations, but this description gives no differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 the many sibling scrapecreators tools (e.g., scrapecreators_subreddit_posts, scrapecreators_comments). No conditions, prerequisites, or alternative recommendations are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.