Reddit Q&A to Notion MCP Server

save_reddit_qa_to_notion

Save a Reddit Q&A session with sources to Notion. Store the question, answer, search query, and Reddit post links for later use.

Instructions

Save a Q&A session with Reddit context to Notion database.

Args:
    question (str): The original question asked
    answer (str): The LLM-generated answer
    search_query (str): The Reddit search query used
    reddit_sources (List[Dict[str, str]]): List of Reddit posts with 'title' and 'url' keys

Returns:
    dict: Success/error response

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": {
      "question": "<question>",
      "answer": "<answer>",
      "search_query": "<search_query>",
      "reddit_sources": "<reddit_sources>"
    },
    "name": "save_reddit_qa_to_notion"
  }
}

Input Schema

Name	Required	Description	Default
`answer`	Yes
`question`	Yes
`search_query`	Yes
`reddit_sources`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that this is a write operation to a Notion database and that it returns a success/error dict, which is useful. However it omits auth/permission requirements, duplicate handling, and side effects on existing entries.

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 purpose sentence is front-loaded, and the Args/Returns block is compact and readable. No wasted prose, though the Args section mostly restates the schema field names.

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 four-required-parameter write tool with no annotations and no output schema, the description covers parameters and return shape but leaves out permissions, failure modes, and whether saving is idempotent or creates duplicates. Adequate but with clear gaps.

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 description must compensate, and it does: it names all four parameters with types and even documents the nested structure of reddit_sources ('title' and 'url' keys), which the schema only expresses as a generic string map.

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 opening sentence gives a specific verb (Save), resource (a Q&A session with Reddit context) and destination (Notion database), which clearly separates it from the read-oriented siblings search_reddit, search_posts, and get_top_subreddit_posts. It is clear, though it does not explicitly name those siblings.

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 states what gets saved but offers no when-to-use guidance, no prerequisites, and no mention of when to prefer the sibling search tools first. Usage is only implied by the tool name and destination.

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

Deploy Server