Skip to main content
Glama
goonhammer69

reddit-monitor-mcp

by goonhammer69

get_subreddit_rules

Read-only

Retrieve a subreddit's rules and posting requirements, including required flair and title rules, to ensure your posts comply with community guidelines before publishing.

Instructions

A subreddit's rules plus its posting requirements (flair, title rules) where Reddit exposes them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
subredditYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds a useful conditional behavior: posting requirements are returned only where Reddit exposes them, implying variability. It does not disclose what happens when rules are unavailable, or how the account parameter affects results.

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 a single, direct sentence with no filler. The core content is stated first, and the qualifier about Reddit's exposure limits is appended efficiently.

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?

The output schema and readOnlyHint cover return structure and safety, so the description does not need to explain those. It is nevertheless incomplete for a smooth call because the account parameter is undocumented and no guidance distinguishes this tool from nearby siblings. It is adequate but not thorough.

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

Parameters2/5

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

Schema description coverage is 0%, so the description bears the burden of explaining parameters. It implicitly covers subreddit through the tool's subject matter, but the account parameter is entirely unexplained, and no format or constraints are provided for subreddit.

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?

The description clearly identifies the resource (a subreddit's rules) and the additional content (posting requirements like flair and title rules), which differentiates it from siblings such as get_subreddit_sidebar or get_subreddit_feed. However, it is phrased as a noun phrase rather than a verb-driven action, and 'where Reddit exposes them' introduces mild ambiguity about scope.

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?

There is no explicit guidance about when to use this tool versus alternatives. The distinction from get_subreddit_sidebar or get_subreddit_feed is only implicit through the subject matter, with no stated conditions or exclusions.

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

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/goonhammer69/reddit-monitor-mcp'

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