A
licenseNot graded
qualityF
maintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.
6
MIT
mcp-meta-brand-presence-mapper
by mambalabsdev
MCP-Server für den Instagram Threads Facebook Brand Presence Mapper-Actor von Mamba Labs auf Apify.
Löst eine Unternehmensdomain in ihre Instagram-, Threads- und Facebook-Konten mit Follower- und Beitragszahlen auf.
Was es tut
Löst eine Unternehmensdomain in ihre Instagram-, Threads- und Facebook-Konten mit Follower- und Beitragszahlen auf – als eine flache, Clay-bereite Zeile. Der Threads-Handle wird ohne zusätzliche Ermittlungskosten aus dem aufgelösten Instagram-Handle abgeleitet. Instagram- und Threads-Zahlen werden von Meta gerundet, und die Zeile enthält sowohl den gerundeten Ganzzahlwert als auch die plattformeigene Anzeigezeichenfolge. Facebook ist Best Effort: Meta zeigt anonymen Clients eine Login-Sperre, daher ist „blockiert“ dort eine normale Antwort und niemals eine Null. Nur lesend; erfordert ein APIFY_TOKEN und verbraucht pro Aufruf Apify-Credits.
Related MCP server: mcp-domain-to-linkedin-url-resolver
Schnellstart
Fügen Sie dies zu Ihrer MCP-Client-Konfiguration hinzu:
{
"mcpServers": {
"mamba-meta-brand-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-meta-brand-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Voraussetzungen
Node.js 18 oder neuer
Ein Apify-API-Token von console.apify.com/account/integrations
Der Actor wird pro Ereignis abgerechnet und verbraucht pro Aufruf Apify-Credits. Die Preise finden Sie auf der Actor-Seite.
Beispiel-Prompts
„Ermitteln Sie die Instagram- und Threads-Followerzahlen für glossier.com.“
„Hat oatly.com Threads bereits übernommen, und wie viele Beiträge haben sie?“
„Finden Sie die Facebook-Seite für everlane.com.“
Tool und Eingaben
Tool: map_meta_brand_presence
Eingabe | Typ | Bedeutung |
| string | Nackte Unternehmensdomain, z. B. shopify.com. Geben Sie dies oder einen Handle an. Mit einer Domain führt der Actor eine vollständige Suche durch; mit einem Handle springt er direkt zu |
| string | Optional. Verbessert die Suchgenauigkeit und ist das, wogegen das Identitätsgate ein gefundenes Profil prüft. Die Angabe reduziert also Fehltreffer. |
| string | Optional. Der Instagram-Handle mit oder ohne führendes @. Durch die Angabe wird die Instagram-Suche übersprungen UND Threads erhält seinen Handle kostenlos, da Th |
| array | Welche der drei Meta-Oberflächen zugeordnet werden sollen. Standard sind alle drei. Facebook wegzulassen ist die übliche Wahl: Es ist die unzuverlässigste der drei und es ko |
| boolean | Bei „true“ (Standard) wird die Profilseite abgerufen und die Zahlen extrahiert. Setzen Sie „false“, um nur die Profil-URL aufzulösen, was günstiger ist und ben |
| boolean | Bei „false“ (Standard) wird eine erfolgreiche Suche sieben Tage lang zwischengespeichert und wiederverwendet. Setzen Sie „true“, um einen neuen Abruf zu erzwingen. Wird aus Kompatibilitätsgründen als Zeichenfolge an Clay gesendet |
Ausgabe lesen
Jede Zeile enthält ein plattformspezifisches _status-Feld, und dieses Feld sollte zuerst gelesen werden. Das Vokabular ist in der gesamten Mamba-Labs-Social-Familie gleich:
Status | Bedeutung |
| abgerufen und geparst, der Wert ist vorhanden |
| wir haben nachgesehen und es gibt kein solches Profil |
| das Profil existiert und der Wert ist für uns nicht abrufbar |
| die Plattform hat uns abgewiesen, später erneut versuchen |
| wir haben ein echtes Profil gefunden und es gehört jemand anderem |
| Sie haben diese Plattform nicht angefordert |
false und null sind niemals austauschbar. false bedeutet, wir haben nachgesehen und die Antwort ist nein. null bedeutet, wir konnten nicht nachsehen. Wenn Sie nach Unternehmen ohne Präsenz filtern, filtern Sie nach false, denn null-Zeilen sind unbekannt und nicht abwesend.
Vollständige Actor-Dokumentation
apify.com/mambalabs/meta-brand-presence-mapper
Mamba Labs GTM Suite
Mamba Labs baut eine Flotte von GTM-Anreicherungs-Actors, die eine gemeinsame flache, Clay-bereite Ausgabekonvention teilen, sodass ihre Zeilen ohne Bereinigungsschritt über company_domain verbunden werden können. Komplette Flotte: apify.com/mambalabs
Lizenz
MIT
Available Tools
1 toolmap_meta_brand_presenceMap Instagram Threads and Facebook PresenceARead-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
| Name | Required | Description | Default |
|---|---|---|---|
| handle | No | Optional. 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). | |
| platforms | No | 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 costs a fetch to find that out. | |
| 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. | |
| 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. | |
| 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. |
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 tool update
v1.0.0- First observed
map_meta_brand_presence
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
Related MCP Connectors
Domain & brand intelligence: company enrichment, tech stack detection, brand research.
Enrich any domain into a full company profile with firmographics and buying signals.
WHOIS/RDAP, DNS, SSL, live subdomains with IPs, and SPF/DMARC/DKIM for any domain.
Company social handles (LinkedIn, Instagram, X, Facebook, YouTube) via Apify MCP.
Related MCP Servers
- AlicenseAqualityAmaintenanceResolves a company domain to its LinkedIn company page URL. Lightweight enrichment tool for sales and prospecting workflows.152 npm2MIT
- AlicenseAqualityAmaintenanceMaps a company domain to its official social media URLs and follower counts across LinkedIn, X, Instagram, Facebook, and YouTube.138 npmMIT
- AlicenseAqualityBmaintenanceResolves TikTok handles or company domains to brand accounts, returning follower, like, video counts, verification status, and more.128 npmMIT