Skip to main content
Glama
karanb192

Reddit Buddy MCP

by karanb192

get_post_details

Read-only

Retrieve a Reddit post and its comments by providing the post URL or ID. Supports sorting and depth options for comments.

Instructions

Fetch a Reddit post with its comments. Requires EITHER url OR post_id. IMPORTANT: When using post_id alone, an extra API call is made to fetch the subreddit first (2 calls total). For better efficiency, always provide the subreddit parameter when known (1 call total).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFull Reddit URL (alternative to post_id)
post_idNoReddit post ID (e.g., "1abc2d3")
subredditNoSubreddit name (optional with post_id, but more efficient if provided)
comment_sortNobest
comment_depthNoDefault 3, range (1-10). Override ONLY IF user specifies.
comment_limitNoDefault 20, range (1-500). Change ONLY IF user asks.
extract_linksNo
max_top_commentsNoDefault 5, range (1-20). Change ONLY IF user requests.
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds value by detailing extra API call behavior and efficiency gains with subreddit, which annotations lack.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then requirements, then an important efficiency note. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers key behavioral aspects for 8 parameters and no output schema. Includes efficiency and required argument strategies, though lacks detail on return format or extract_links.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%; description enhances understanding by explaining the trade-off between url and post_id parameters, and the efficiency benefit of providing subreddit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Fetch a Reddit post with its comments', specifying verb and resource. Differentiates from sibling tools like browse_subreddit and search_reddit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly requires url OR post_id, and advises providing subreddit for efficiency. Provides clear context on when and how to use, with an alternative strategy.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karanb192/reddit-mcp-buddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server