reddit_comment
Post a comment on Reddit by providing authentication, the parent post or comment ID, and the comment text.
Instructions
Post a comment on Reddit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| access_token | Yes | ||
| parent_id | Yes | ||
| text | Yes |
Post a comment on Reddit by providing authentication, the parent post or comment ID, and the comment text.
Post a comment on Reddit.
| Name | Required | Description | Default |
|---|---|---|---|
| access_token | Yes | ||
| parent_id | Yes | ||
| text | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It mentions 'Post a comment' but does not disclose that authentication is required (access_token), rate limits, or what happens on success/failure. The schema shows required params, but the description adds no behavioral context.
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?
The description is a single sentence with no fluff, but it is too brief. It could be structured to front-load key information (e.g., purpose then context). Currently, it lacks structure for quick scanning.
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?
Given no output schema and low schema coverage, the description should explain return values (e.g., returns the comment ID?). It does not address error handling or expected behavior, leaving the agent underinformed.
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?
Schema description coverage is 0%, yet the description provides no information about parameters. The three required fields (access_token, parent_id, text) are not explained. For instance, what format should parent_id follow? Are there length limits on text? No guidance.
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 clearly states the action ('Post a comment') and the resource ('on Reddit'). However, it does not differentiate from sibling tool 'reddit_post', which might be for submitting new posts. Adding 'reply to an existing post or comment' would improve specificity.
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?
No guidance on when to use this tool versus alternatives like 'reddit_post' or 'reddit_vote'. The description lacks context about prerequisites (e.g., need a parent_id for a reply) or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server