Skip to main content
Glama
eliasbiondo

Reddit MCP Server

by eliasbiondo

reddit_get_post

Retrieve complete Reddit post details and nested comment threads using a permalink to analyze discussions or extract content.

Instructions

Get full details of a Reddit post including its comment tree.

Args: permalink: Reddit permalink path (e.g., '/r/Python/comments/abc123/my_post/')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
permalinkYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function 'reddit_get_post' which executes the tool logic by calling the PostService.
    async def reddit_get_post(
        permalink: str,
        ctx: Context,
    ) -> dict[str, Any]:
        try:
            result = await service.get_post(permalink)
            return McpSerializer.serialize(result)
        except Exception as e:
            McpErrorMapper.map(e, "reddit_get_post")
  • Registration of the 'reddit_get_post' tool using the FastMCP decorator.
    @mcp.tool(
        name="reddit_get_post",
        description=(
            "Get full details of a Reddit post including its comment tree.\n\n"
            "Args:\n"
            "    permalink: Reddit permalink path "
            "(e.g., '/r/Python/comments/abc123/my_post/')"
        ),
    )
Behavior3/5

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

No annotations provided, so description carries full burden. It adequately discloses the comment tree inclusion (important behavioral trait not obvious from 'get post'), but omits auth requirements, rate limits, comment depth limits, and error handling for invalid permalinks.

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

Conciseness4/5

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

Well-structured with purpose front-loaded in the first sentence, followed by clear Args documentation. No redundant text; the example permalink efficiently illustrates the expected format without verbosity.

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

Completeness3/5

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

Appropriate for a single-parameter read operation with output schema present. Covers core functionality and return data shape (comment tree), but given lack of annotations, should mention authentication requirements or API rate considerations to be complete.

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?

With 0% schema description coverage, the Args block compensates effectively by documenting the permalink parameter with both semantic description ('Reddit permalink path') and format example ('/r/Python/comments/abc123/my_post/'), clarifying expected input structure.

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

Purpose4/5

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

Clear specific verb ('Get') + resource ('Reddit post') + scope ('full details including its comment tree'). Distinguishes implicitly from siblings via the permalink-based retrieval (vs. search/list operations), though explicit differentiation is absent.

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

Usage Guidelines2/5

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

No explicit when-to-use guidance, prerequisites, or alternatives mentioned. User must infer this is for direct permalink retrieval versus searching or listing from sibling tool names alone.

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/eliasbiondo/reddit-mcp-server'

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