reddit_post
Fetch a normalized Reddit post entry using a post ID or t3_ ID.
Instructions
Get Reddit post. Returns a normalized public Reddit post entry.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Reddit post id or t3_ id |
Fetch a normalized Reddit post entry using a post ID or t3_ ID.
Get Reddit post. Returns a normalized public Reddit post entry.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Reddit post id or t3_ id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden but only states 'Returns a normalized public Reddit post entry.' It does not disclose authentication needs, rate limits, or any side effects. The term 'normalized' is vague.
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?
Two concise sentences front-load the purpose. Could be slightly more efficient, but no unnecessary words.
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?
No output schema is provided, but the description hints at a 'normalized public Reddit post entry'. This is adequate for a simple retrieval tool, though more detail on return structure would help.
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 coverage is 100% for the single parameter 'id' with a clear description. The tool description adds 'normalized public Reddit post' but does not provide additional parameter details beyond the schema, meeting the baseline.
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 ('Get') and the resource ('Reddit post'), and it distinguishes from sibling tools like reddit_search (searching) and reddit_comments (comments on a post) by specifying a single post by ID.
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. It does not mention that this tool is for retrieving a specific post by ID, while reddit_search or reddit_subreddit_posts are for finding posts by query or subreddit.
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/Crawlora-org/crawlora-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server