Reddit Q&A to Notion MCP Server

get_top_subreddit_posts

Retrieve top posts and comments from specified subreddits by time period to support Reddit Q&A research and Notion workflows.

Instructions

Get top posts from specified subreddits.

Args:
    subreddits (str): Subreddit name(s) separated by '+' (e.g., "redditdev+learnpython")
    limit (int): Number of posts to retrieve (default: 10)
    comment_limit (int): Number of comments to retrieve for each post (default: 5)
    time_filter (str): One of: "all", "day", "hour", "month", "week", "year" (default: "week")

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

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": {
      "subreddits": "<subreddits>"
    },
    "name": "get_top_subreddit_posts"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`subreddits`	Yes
`time_filter`	No	week
`comment_limit`	No

Output 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 behavioral burden. It does disclose that comments are fetched per post via comment_limit and that the return is a list of dicts, but it says nothing about Reddit API auth requirements, rate limits, error behavior, or pagination — significant gaps for a network-backed read tool.

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?

Google-style docstring with the purpose front-loaded and parameters grouped compactly; no filler sentences. The Returns block is somewhat redundant given an output schema exists, but it is brief.

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?

An output schema exists so return-value explanation is not required, and all four parameters are at least named. Still, the limit default mismatch and the absence of any guidance on how 'top' is ranked relative to time_filter leave the definition only minimally 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?

Schema description coverage is 0%, so the Args block is doing real work: it documents the '+' separator syntax for subreddits and enumerates the valid time_filter values. It is docked one point because the stated default for limit ('10') conflicts with the schema default of 5, which can mislead an agent.

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 first sentence gives a specific verb and resource ('Get top posts from specified subreddits'), so the core action is unambiguous. However, it never distinguishes itself from siblings like search_posts or search_reddit, leaving the agent to infer that this is a ranking-based (rather than query-based) retrieval.

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 when-to-use guidance, no when-not-to-use, and no mention of alternatives. An agent cannot tell from the text whether to reach for this tool or search_posts/search_reddit for a given request.

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

Deploy Server