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

Apify 上の Mamba Labs Instagram Threads Facebook Brand Presence Mapper アクターのための MCP サーバー。

企業ドメインを Instagram、Threads、Facebook のアカウントに解決し、フォロワー数と投稿数を取得します。

機能

企業ドメインを Instagram、Threads、Facebook のアカウントに解決し、フォロワー数と投稿数を、フラットな Clay 対応の1行として返します。Threads のハンドルは、解決済みの Instagram ハンドルから追加のディスカバリコストなしで導出されます。Instagram と Threads のカウントは Meta によって丸められ、行には丸められた整数とプラットフォーム独自の表示文字列の両方が含まれます。Facebook はベストエフォートです。Meta は匿名クライアントにログインウォールを表示するため、blocked は通常の応答であり、ゼロになることはありません。読み取り専用です。APIFY_TOKEN が必要で、呼び出しのたびに Apify クレジットを消費します。

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

クイックスタート

MCP クライアント設定に次を追加します:

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

前提条件

このアクターは従量課金制で、呼び出しのたびに Apify クレジットを消費します。料金はアクターページをご覧ください。

プロンプト例

  • 「glossier.com の Instagram と Threads のフォロワー数を取得して。」

  • 「oatly.com は Threads を導入済み？ 投稿数は？」

  • 「everlane.com の Facebook ページを見つけて。」

ツールと入力

ツール: map_meta_brand_presence

入力

型

意味

company_domain

string

ベアの企業ドメイン（例: shopify.com）。これまたはハンドルを指定します。ドメインを指定するとアクターが完全なディスカバリを実行し、ハンドルを指定すると直接

company_name

string

任意。検索精度が向上し、アイデンティティゲートが検出したプロフィールを照合する際の基準にもなります。指定すると誤一致が減ります。

handle

string

任意。先頭の @ の有無を問わない Instagram ハンドル。指定すると Instagram のディスカバリをスキップし、Threads のハンドルも無料で取得できます。Th

platforms

array

マッピングする Meta の3つのサーフェスのうちどれか。デフォルトは3つすべてです。Facebook を外すのが一般的です。最も信頼性が低く、また co

includeFollowerCounts

boolean

"true"（デフォルト）の場合、プロフィールページを取得してカウントを抽出します。プロフィール URL のみを解決するには "false" に設定します。安価で必

skipCache

boolean

"false"（デフォルト）の場合、成功したルックアップは7日間キャッシュされ再利用されます。強制的に再取得するには "true" に設定します。Clay 互換のため文字列として送信されます

出力の読み方

各行にはプラットフォームごとの _status フィールドがあり、最初に読むべきフィールドです。語彙は Mamba Labs のソーシャルファミリー全体で共通です：

ステータス

意味

ok

取得・解析済み、値あり

not_found

検索したがプロフィールが存在しない

not_extractable

プロフィールは存在するが、値が取得できない

blocked

プラットフォームに拒否された。後で再試行する価値あり

identity_mismatch

実在するプロフィールを見つけたが、それは他人のもの

skipped

このプラットフォームはリクエストされていない

false と null は決して同じ意味ではありません。 false は検索した結果「いいえ」という意味です。null は検索できなかったことを意味します。存在しない企業をフィルタリングする場合は、false でフィルタリングしてください。null の行は「不在」ではなく「不明」だからです。

アクターの完全なドキュメント

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

Mamba Labs GTM スイート

Mamba Labs は、フラットな Clay 対応出力形式を共有する GTM エンリッチメントアクター群を開発しています。そのため、クリーニング不要で company_domain をキーに行を結合できます。全アクター一覧: apify.com/mambalabs

ライセンス

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.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