mcp-reddit-brand-presence-mapper

Map Reddit Brand Presence

map_reddit_brand_presence

Read-onlyIdempotent

Resolve a company domain to its official subreddit and optionally sample recent public brand mentions. Returns the subreddit URL, subscriber count, creation date, and mention sample.

Instructions

Resolve a company domain to that company's official subreddit and, optionally, sample recent public mentions of the brand. Returns the subreddit URL, subscriber count, creation date and a mention sample, as one flat Clay ready row. IMPORTANT LIMITATION: Reddit refuses a share of requests however they are routed. Measured on the platform 2026-08-23 across nine companies over residential connections, the subreddit feed was readable for four and refused for five, and the mention feed the same. A refusal is reported as blocked, never as an empty result or a zero, and is worth retrying. Subscriber counts need the caller's own Reddit app credentials (redditClientId and redditClientSecret), because Reddit refuses every unauthenticated JSON route. Use it for one company at a time; it does not monitor Reddit over time or return post text. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

Name	Required	Description
`handle`	No	Optional. The subreddit name with or without the r/ prefix, for example stripe. Supplying it skips discovery.
`skipCache`	No	When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibility.
`company_name`	No	Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
`mentionQuery`	No	What to search Reddit for when measuring brand mentions. Defaults to your domain in quotes, which is measured far more precise than the brand name: a bare search for "stripe" returns r/Horses and r/MyHeroAcadamia because Reddit matches the English word, while "stripe.com" returns developer subreddits.
`company_domain`	No	Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to the fetch.
`redditClientId`	No	YOUR OWN Reddit app client id. Free to create at reddit.com/prefs/apps. This is the only route to a subscriber count: Reddit returns 403 on every unauthenticated JSON route. Leave empty and everything else still works.
`includeMentions`	No	When "true" (default) a site wide mention sample is pulled alongside the subreddit. Set "false" for the official subreddit only, which is one fetch instead of two. Sent as a string for Clay compatibility.
`redditClientSecret`	No	YOUR OWN Reddit app client secret, paired with the client id above. Used for your run only and never stored.
`includeFollowerCounts`	No	When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and needs no proxy. Sent as a string for Clay compatibility.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.1Oct 15, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.0.0Sep 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent/non-destructive): it discloses that Reddit refuses a measurable share of requests, that refusals surface as 'blocked' rather than empty/zero, that retrying is worthwhile, and that subscriber counts require caller-supplied Reddit app credentials. This is exactly the operational context an agent needs and cannot get from structured fields.

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-loads purpose, then the limitation and usage constraints, then prerequisites. Dense but well organized; the measured-refusal statistic is slightly verbose but earns its place by justifying the retry guidance.

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

Completeness5/5

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

With nine optional parameters, no annotations for output and no output schema, the description compensates by describing the returned row, the credential requirement, the refusal semantics, and the per-call cost. An agent has everything needed to invoke and interpret results.

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 100% and each parameter is already well documented, so the schema carries the burden. The description reinforces why credentials matter and that domain-based discovery differs from handle-based fetch, but it adds little parameter syntax beyond what the schema states. Baseline 3 applies.

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?

States a specific verb and resource: resolve a company domain to its official subreddit and optionally sample brand mentions. It also names the shape of the result (subreddit URL, subscriber count, creation date, mention sample) so the agent knows exactly what comes back. There are no siblings, but the scope is unambiguous.

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 bounds usage: 'Use it for one company at a time; it does not monitor Reddit over time or return post text.' It also states the read-only nature, the APIFY_TOKEN prerequisite, and that each call consumes Apify credits. When-to-use, when-not-to-use, and cost are all covered.

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

Deploy Server

Other Tools

map_reddit_brand_presenceA