scrapecreators_post_comments
Post Comments
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Reddit post URL | |
| trim | No | Set to true for a trimmed down version of the response | |
| cursor | No | Cursor to get more comments, or replies. |
xpay✦ Marketing Collection
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- 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 carries full burden but says nothing about side effects, safety, auth, or return behavior. 'Post Comments' gives zero behavioral information and could mislead about whether it writes data.
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?
At two words, it's under-specified rather than concise. It lacks a verb and any useful structure, making it less informative than a simple sentence like 'Scrape comments from a Reddit post URL.'
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?
Given no output schema and no annotations, the description should explain return values and pagination. It does neither, making the tool's behavior opaque and incomplete.
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%, with descriptions for url, trim, and cursor. The description adds no param semantics, but the schema already documents them, so baseline of 3 applies.
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?
Description 'Post Comments' is a noun phrase that merely restates part of the tool name without a verb indicating action (e.g., scrape, retrieve). It is ambiguous between posting comments and retrieving comments on a post, and does not distinguish from sibling tools like scrapecreators_comments.
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 provided on when to use this tool over alternatives. There is no mention of Reddit-specific behavior, prerequisites, or comparison to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.