Skip to main content
Glama
deenesjakoruzh
mambalabsdev

mcp-meta-brand-presence-mapper

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Instagram Threads Facebook Brand Presence Mapper MCP Server

Smithery Glama score npm version npm downloads license

MCP server for the Mamba Labs Instagram Threads Facebook Brand Presence Mapper actor on Apify.

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts.

What it does

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Related MCP server: mcp-domain-to-linkedin-url-resolver

Quick start

Add this to your MCP client configuration:

{
  "mcpServers": {
    "mamba-meta-brand-presence-mapper": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-meta-brand-presence-mapper"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Prerequisites

The actor is pay per event and consumes Apify credits per call. Pricing is on the actor page.

Example prompts

  • "Get the Instagram and Threads follower counts for glossier.com."

  • "Has oatly.com adopted Threads yet, and how many posts do they have?"

  • "Find the Facebook Page for everlane.com."

Tool and inputs

Tool: map_meta_brand_presence

Input

Type

Meaning

company_domain

string

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

company_name

string

Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.

handle

string

Optional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Th

platforms

array

Which of the three Meta surfaces to map. Default is all three. Dropping Facebook is the common choice: it is the least reliable of the three and it co

includeFollowerCounts

boolean

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 need

skipCache

boolean

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 compatibi

Reading the output

Every row carries a per platform _status field, and it is the field to read first. The vocabulary is the same across the whole Mamba Labs social family:

Status

Meaning

ok

fetched and parsed, the value is there

not_found

we looked and there is no such profile

not_extractable

the profile exists and the value is not on the wire to us

blocked

the platform refused us, worth retrying later

identity_mismatch

we found a real profile and it belongs to someone else

skipped

you did not ask for this platform

false and null are never interchangeable. false means we looked and the answer is no. null means we could not look. If you filter for companies with no presence, filter on false, because null rows are unknown rather than absent.

Full actor documentation

apify.com/mambalabs/meta-brand-presence-mapper

Mamba Labs GTM Suite

Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay ready output convention, so their rows join on company_domain with no cleaning step. Full fleet: apify.com/mambalabs

License

MIT

Available Tools

1 tool
map_meta_brand_presenceMap Instagram Threads and Facebook PresenceA
Read-onlyIdempotent

Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row. The Threads handle is derived from the resolved Instagram handle at no extra discovery cost. Instagram and Threads counts are rounded by Meta and the row carries both the rounded integer and the platform's own display string. Facebook is best effort: Meta serves a login wall to anonymous clients, so blocked is a normal answer there and never a zero. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametersJSON Schema
NameRequiredDescriptionDefault
handleNoOptional. The Instagram handle with or without the leading @. Supplying it skips Instagram discovery AND gives Threads its handle for free, because Threads handles are Instagram handles (5 of 5 measured).
platformsNoWhich of the three Meta surfaces to map. Default is all three. Dropping Facebook is the common choice: it is the least reliable of the three and it costs a fetch to find that out.
skipCacheNoWhen "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_nameNoOptional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.
company_domainNoBare 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.
includeFollowerCountsNoWhen "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.

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses several non-obvious behaviors: Threads handle is derived from Instagram at no extra cost, counts are rounded by Meta and include both integer and display string, Facebook is best-effort with login walls making 'blocked' a normal response, and each call consumes Apify credits. These are significant operational details an agent needs.

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 yet well-organized: the main purpose is stated first, followed by platform-specific caveats, then parameter behavior and operational constraints. Every sentence adds information and none are redundant with the schema or annotations. It is appropriately sized for the tool's complexity.

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?

Despite having no output schema, the description explains the output format (flat Clay row, rounded counts, display strings), failure modes (Facebook 'blocked'), and prerequisites (APIFY_TOKEN, credits). It also covers pricing implications and caching semantics, making it fully self-sufficient for an agent to call correctly.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds valuable context: the handle is used for both Instagram and Threads ('5 of 5 measured'), platforms can be pruned to reduce cost, cache duration is seven days, and includeFollowerCounts trades completeness for speed and proxy freedom. This goes well beyond the schema's property descriptions.

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 opens with a specific verb and resource: "Resolve a company domain to its Instagram, Threads and Facebook accounts with follower and post counts, as one flat Clay ready row." It clearly states what the tool produces and differentiates its behavior for each platform, leaving no ambiguity about its function.

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?

Though there are no sibling tools, the description provides detailed guidance on when to use specific options: supplying a handle skips discovery, dropping Facebook is common due to unreliability, includeFollowerCounts=false is cheaper and needs no proxy, and skipCache forces fresh fetches. This qualifies as clear usage context and decision support.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedmap_meta_brand_presence
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The sole tool has a clear, singular purpose of mapping a domain to Meta platform accounts.

Naming Consistency5/5

The tool name follows a consistent verb_noun pattern ('map_meta_brand_presence'), which is descriptive and predictable, though there is only one example to assess.

Tool Count3/5

A single tool feels thin for a server, even if the task is narrowly focused. The server could benefit from splitting functionality (e.g., separate tools for Instagram, Threads, Facebook) or adding related capabilities, but the count is not unreasonable for a dedicated mapper.

Completeness4/5

The tool covers the core workflow of resolving a domain to social accounts and retrieving follower/post counts, with a noted limitation on Facebook due to login walls. However, it handles this limitation explicitly, so the surface is functionally complete for its stated purpose, though slightly constrained by external factors.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers