mcp-reddit-brand-presence-mapper

Map Reddit Brand Presence

map_reddit_brand_presence

Read-onlyIdempotent

Resolve a company domain to its official subreddit and sample recent public brand mentions. Get subreddit URL, subscriber count, creation date, and mention sample as one Clay-ready row.

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's RSS routes return HTTP 403 to Apify platform IP ranges as measured on 2026-08-22, so subreddit discovery resolves but cadence and mention fields come back marked blocked rather than populated. The row reports blocked rather than an empty result, so an absence is never mistaken for a finding. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

TableJSON 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.

First observedv1.0.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing the known HTTP 403 limitation on Apify IP ranges, the fact that blocked fields are reported as blocked rather than empty, the APIFY_TOKEN requirement, and per-call Apify credit consumption. This prevents an agent from misinterpreting missing mention data as a genuine absence.

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 dense but efficient: purpose, the critical limitation, output shape, and operational requirements are all packed into a tight paragraph with no filler. Every sentence adds actionable information for an agent.

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?

Even though there is no output schema, the description names the returned fields and explains the blocked-state behavior, so an agent knows what to expect. Combined with the fully described input schema, required-parameter absence, and annotation signals, nothing critical is missing for correct invocation.

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%, so the input schema already fully documents all nine parameters. The prose reinforces operational choices like domain versus handle and the client-id route to subscriber counts, but it does not substantially add new meaning beyond what the schema already provides.

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 uses a specific verb and resource ('Resolve a company domain to that company's official subreddit') and explicitly lists the returned artifacts: subreddit URL, subscriber count, creation date, and mention sample. It also clarifies the main operational distinction between domain-based discovery and handle-based skipping, so it is far more informative than the tool title.

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

Usage Guidelines4/5

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

Clear usage context is provided: supplying a handle skips discovery, supplying a domain triggers full discovery, setting includeFollowerCounts to false performs a cheaper URL-only fetch, and includeMentions false avoids a second request. There are no sibling tools to contrast against, and there is no explicit when-not-to-use statement, so it stops short of a 5.

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