Skip to main content
Glama
osamuelnovaes

mcp-reddit-publisher

Search subreddits

search_subreddits

Search Reddit communities to find audience fit before posting.

Instructions

Searches Reddit communities by query to help find audience fit before posting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does not explain what is returned (e.g., subreddit names, descriptions), sorting, pagination, or rate limits, leaving the agent underinformed.

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?

The description is a single, concise sentence with no redundant information. While it is efficient, some additional detail on parameters or behavior would improve utility without sacrificing conciseness.

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

Completeness2/5

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

Given the tool has 2 parameters, no output schema, and no annotations, the description is incomplete. It fails to clarify the return format, error handling, or what constitutes a valid query, which is critical for an AI agent to use it correctly.

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 coverage is 0%, meaning the description must explain parameters. It only mentions 'query' indirectly ('by query') but does not describe the 'query' parameter's semantics (e.g., case sensitivity, partial matching) or the 'limit' parameter at all.

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 clearly states the tool searches Reddit communities by query, with a specific use case of finding audience fit before posting. It distinguishes from sibling tools like 'get_subreddit_rules' and 'submit_text_post'.

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

Usage Guidelines4/5

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

The description implies usage for audience research before posting, which is a reasonable use case. However, it does not explicitly state when not to use or mention alternatives, though the context of sibling tools helps.

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