Reddit Q&A to Notion MCP Server

search_reddit

Search Reddit site-wide for posts matching a query, retrieving discussions and comments to find answers. Use to gather Q&A content for Notion.

Instructions

Search for posts across all subreddits (site-wide search).

Args:
    query (str): Search query
    limit (int): Number of posts to retrieve (default: 5)
    comment_limit (int): Number of comments to retrieve for each post (default: 5)
    sort (str): One of: "relevance", "hot", "top", "new", "comments" (default: "relevance")

Returns:
    List[Dict[str, Any]]: List of dictionaries containing post information

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	relevance
`limit`	No
`query`	Yes
`comment_limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read/search operation and notes that comment_limit controls comments fetched per post, but says nothing about rate limits, auth requirements, pagination, or how results are ordered/truncated.

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?

Front-loaded one-line purpose followed by a compact Args block; every line earns its place. Slightly boilerplate docstring formatting but nothing wasteful.

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?

For a 4-parameter search tool with an output schema, the parameter documentation is sufficient and the return value need not be re-explained. It lacks usage context and any behavioral caveats, so it is adequate but not complete for choosing between siblings.

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 0%, so the description must compensate and largely does: it documents query, limit, comment_limit, and sort with meanings, defaults, and the full enum list for sort ('relevance','hot','top','new','comments') that the schema omits. Only minor gaps remain (e.g., interaction between limit and comment_limit).

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?

States a clear verb (search) and resource (posts across all subreddits), and the parenthetical 'site-wide search' scopes it against subreddit-specific siblings like get_top_subreddit_posts. However, it never distinguishes itself from the similarly named sibling search_posts, leaving an ambiguity.

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?

The description says what it does but gives no when-to-use guidance, no prerequisites, and no mention of the sibling search_posts that an agent must choose between. Usage is only implied by the name.

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

Deploy Server