Skip to main content
Glama
Sign In
MCP Reddit Server

MCP Reddit Server

by Aanerud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

reddit_info

Retrieve subreddit details such as subscriber count and description by using the subreddit name without the 'r/' prefix.

Instructions

Get subreddit info (subscribers, description).

Args: subreddit: Subreddit name (without r/)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subreddit": "<subreddit>"
    },
    "name": "reddit_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
subredditYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It makes clear this is a read operation ('Get') and discloses the returned content ('subscribers, description'). It does not address error cases, authentication, or rate limits, but for a simple metadata lookup the provided behavior is reasonably transparent.

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?

The description is extremely compact and front-loaded: the core purpose and return fields appear first, followed by the parameter clarification. Every sentence earns its place with no redundancy.

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?

For a single-parameter read tool with an output schema, the description covers the purpose, returned fields, and the only input's formatting. It does not explicitly differentiate from the sibling post-retrieval tools, but this is a minor gap given the low complexity and clear resource scope.

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?

The input schema has 0% description coverage, so the description must compensate. It does by explaining the parameter format: 'Subreddit name (without r/)'. This adds meaningful guidance beyond the bare schema property and fully covers the only parameter.

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?

The description states a specific verb and resource: 'Get subreddit info', and names the exact fields returned ('subscribers, description'). This clearly distinguishes the tool from sibling feed/post-retrieval tools such as reddit_hot and reddit_post, which are about content rather than subreddit metadata.

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving subreddit metadata rather than posts, but it does not explicitly state when to prefer it over siblings or mention any exclusions. It provides usable but implicit usage guidance only.

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

Deploy Server

Other Tools