Skip to main content
Glama
mcp-meta-brand-presence-mapper

mcp-meta-brand-presence-mapper

Instagram Threads Facebook Brand Presence Mapper MCP Server

Smithery Glama score npm version npm downloads license

MCP 服务器,用于 Apify 上的 Mamba Labs Instagram Threads Facebook Brand Presence Mapper actor。

将公司域名解析为它的 Instagram、Threads 和 Facebook 账号,并包含粉丝数和帖子数。

它能做什么

将公司域名解析为它的 Instagram、Threads 和 Facebook 账号,并返回粉丝数和帖子数,作为一条扁平、可直接导入 Clay 的记录。Threads 的 handle 由解析出的 Instagram 用户名直接得出,无需额外的发现成本。Instagram 和 Threads 的计数由 Meta 四舍五入,记录中同时包含四舍五入后的整数和平台自己的展示字符串。Facebook 是尽力而为:Meta 对匿名访客设置登录墙,因此 blocked 是该平台正常返回的答案,而绝不是零。该服务为只读;需要 APIFY_TOKEN,并且每次调用都会消耗 Apify Credits。

Related MCP server: Company Social Presence Mapper MCP Server

快速开始

在你的 MCP 客户端配置中添加以下内容:

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

先决条件

该 actor 按事件付费,每次调用消耗 Apify Credits。价格信息请actor 页面。

示例提示词

  • "获取 glossier.com 的 Instagram 和 Threads 粉丝数。"

  • "oatly.com 是否已采用 Threads?他们发布了几条帖子?"

  • "查找 everlane.com 的 Facebook 页面。"

工具与输入

工具:map_meta_brand_presence

输入

类型

含义

company_domain

string

裸域名,例如 shopify.com。请提供此值或一个 handle。提供域名时,actor 会执行完整发现;提供 handle 时,它会直接跳转至

company_name

string

可选。提高搜索准确性,也是身份检查门锁定对已发现 profile 进行核对的依据,因此提供它可减少错误匹配。

handle

string

可选。Instagram 用户名(可带或不带开头的 @)。提供它可跳过 Instagram 发现,并免费为 Threads 获得其 handle,因为 Th

platforms

array

要映射三个 Meta 平台中的哪些。默认全部映射。放弃 Facebook 是常见选择:它是三者中最不可靠的,并且它 co

includeFollowerCounts

boolean

当为“true”(默认)时,会获取并解析个人资料中的粉丝数。设置为“false”则仅解析个人资料 URL,成本更低且需要

skipCache

boolean

当为“false”(默认)时,外部成功结果会被缓存并复用 7 天。设置为“true”会强制重新获取。以字符串形式发送以兼容 Clay compatibi

解读输出

每行都包含一个按平台区分的 _status 字段,也是首先需要读取的字段。整个 Mamba Labs 社交产品线统一使用相同的词汇:

状态

含义

ok

已抓取并解析,值已存在

not_found

我们查找过,但没有发现该 profile

not_extractable

profile 存在,但该值不在返回的数据中

blocked

平台拒绝了我们,是否有稍后重试的价值

identity_mismatch

找到了真实 profile,但它属于其他人

skipped

你没有请求此平台

false 和 null 永远不能互换。 false 表示我们查过,答案是“没有”;null 表示我们无法查询。如果你想筛选没有对应“存在”的公司,应筛选 false,因为 null 行代表“未知”,而非“缺失”。

完整的 actor 文档

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

Mamba Labs GTM Suite

Mamba Labs 构建了一套 GTM 数据增强 actor,它们共享统一的扁平化、直接可被 Clay 使用的输出格式,因此可以通过 company_domain 将各行连接在一起,无需清理步骤。完整工具集:apify.com/mambalabs

许可证

MIT

Available Tools

1 tool
map_meta_brand_presenceMap Instagram Threads and Facebook PresenceA
Idempotent

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.

Inputs: handle, platforms, skipCache, company_name, +3 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection or overlap. Its purpose (domain → Meta account resolution) is unambiguous from the name and description.

    Naming Consistency5/5

    The single tool follows a clean verb_noun snake_case pattern (map_meta_brand_presence) that clearly states the action and resource. With one tool there is no convention mixing to penalize.

    Tool Count3/5

    A single tool is thin even for a narrow enrichment server, sitting below the typical 3-15 range. The scope (one read-only resolution call) plausibly justifies it, but there is no separate tool for batched input or per-platform retries.

    Completeness4/5

    The tool covers the stated domain end to end: domain resolution into Instagram, Threads, and Facebook with counts, and it honestly documents Facebook's best-effort limitation. Minor gaps exist—no bulk/multi-domain input, no retry or credential-check companion tool—but core coverage is solid.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers