B2B Reddit Conversation Monitor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| monitor_reddit_conversationsA | Find Reddit conversations about a company, its competitors, a product category, or a topic, read from public Reddit feeds. mode company: give company_domain (for example smartlead.ai) and get thread and comment rows that name the brand or its competitors, each tagged complaint, praise, comparison, alternative_request, switching, buying_intent, feature_request, or question, with sentiment, a 0 to 100 intent score, and a displacement_signal when a competitor draws a complaint, switch, or alternative request, plus one company summary row with share of voice per competitor. mode category: give category_keywords (for example cold email tools) and get the companies discussed most, with mention counts and sentiment. mode gap: give subreddits and or a topic and get recurring questions grouped by theme, with unanswered counts and the tools the answers named. Tags are rule based. Blocked or empty results come back free with a row_status saying so. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per thread, comment, and summary row returned. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. The mode parameter inside the tool cleanly separates its own behaviors (company, category, gap).
The single name monitor_reddit_conversations follows a clear verb_noun snake_case pattern. With only one tool there is no cross-tool pattern to validate, but nothing is inconsistent.
A single tool is thin for a surface that exposes three distinct analysis modes (company, category, gap); splitting them would make selection clearer. Still, the one tool is well-scoped and not overloaded with unrelated capabilities.
The read-only monitoring domain is reasonably covered across company, category, and gap modes, including sentiment, intent, and share of voice. Gaps remain: no way to fetch a specific thread's full detail, no time-range or pagination controls, and no follow-up retrieval by run ID beyond error reporting.