Skip to main content
Glama
ismailsaoulaj

reddit-mcp-server

by ismailsaoulaj
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

extract_public_opinion

Extract authentic public opinions from Reddit threads by filtering out bots, noise, and low-effort comments. Get direct quote URLs for reliable citation in reports and analysis.

Instructions

DEEP DIVE TOOL: Use this ONLY after finding a relevant post via search tools. This tool extracts PURE human opinions, filtering out noise, bots, and low-effort content. Citations: You MUST use the comment_url for each specific quote in your final report. Pagination: pass next_page_token to continue reading deeper comments. Tokens are provider-prefixed (e.g. 'reddit:30:abc') and only the provider that issued one can continue it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_urlYes
page_tokenNo
max_commentsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe extracted comments.
statusNoStatus of the request.success
messageNoSystem message or warning.
data_sourceNoProvenance of the data: None = official Reddit API, 'arctic_shift' = community archive (metrics may lag live Reddit), 'saved_rss' = the user's private saved-items feed (scores/comment counts unavailable).
meta_contextYesTemporal and spatial context for the AI.
next_page_tokenNoPass this token to the tool again to fetch the next page of comments.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.3.2
    • addedInput schema / properties / max_comments / maximum
      Added value: +100
    • addedInput schema / properties / max_comments / minimum
      Added value: +1
    • addedInput schema / properties / page_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedOutput schema / properties / data_source
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Provenance of the data: None = official Reddit API, 'arctic_shift' = community archive (metrics may lag live Reddit), 'saved_rss' = the user's private saved-items feed (scores/comment counts unavailable)."
+}
    • addedOutput schema / properties / next_page_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pass this token to the tool again to fetch the next page of comments."
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of transparency. It discloses important behaviors: filters bots/noise, requires citations using comment_url, supports pagination via next_page_token, and token ownership restrictions. While it doesn't mention auth or error handling, it covers the core behavioral traits needed for invocation.

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 compact (~70 words) but information-dense, using clear labels (DEEP DIVE TOOL, Citations, Pagination) to organize content. Every sentence serves a purpose: usage, filtering, citation, pagination, token behavior. No fluff or redundancy.

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

Completeness4/5

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

For a tool with no annotations, the description provides a thorough operational picture: purpose, usage context, output requirements, pagination, and token constraints. It leaves out max_comments semantics and explicit platform scope (though 'reddit:' token example hints at Reddit), but overall it's sufficient for selecting and invoking the tool correctly. Output schema exists, so return format needn't be described.

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

Parameters3/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. It explains post_url implicitly and page_token (as next_page_token) well, including provider-prefixed token syntax. However, max_comments is not mentioned at all, leaving that parameter without semantic guidance beyond the schema's numeric constraints. Partial compensation for 2 of 3 parameters.

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 identifies the tool as a 'DEEP DIVE TOOL' that extracts 'PURE human opinions' from a post, filtering noise and bots. It distinguishes itself from sibling search/exploration tools by specifying it operates on a specific post found via search, making its purpose specific and non-overlapping.

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

Usage Guidelines5/5

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

Explicitly states 'Use this ONLY after finding a relevant post via search tools,' which clearly defines when the tool is appropriate. This provides strong guidance on prerequisites and differentiates it from search tools, even if not naming siblings directly.

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

Install Server

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/ismailsaoulaj/reddit-mcp-server'

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