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 서버

Smithery Glama score npm version npm downloads license

Apify의 Mamba Labs Instagram Threads Facebook Brand Presence Mapper 액터용 MCP 서버입니다.

회사 도메인을 인스타그램, 스레드, 페이스북 계정으로 확인하여 팔로워 수와 게시물 수를 제공합니다.

하는 일

회사 도메인을 인스타그램, 스레드, 페이스북 계정으로 확인하여 팔로워 수와 게시물 수를 하나의 평면적인 Clay 준비(row) 형태로 제공합니다. 스레드 핸들은 추가 검색 비용 없이 확인된 인스타그램 핸들에서 파생됩니다. 인스타그램과 스레드 수치는 Meta에 의해 반올림되며, 행에는 반올림된 정수와 플랫폼 자체 표시 문자열이 모두 포함됩니다. 페이스북은 최선 방식(best effort)입니다. Meta는 익명 클라이언트에게 로그인 벽을 제공하므로 차단은 0이 아닌 정상적인 응답입니다. 읽기 전용이며 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의 인스타그램과 스레드 팔로워 수를 가져와 줘."

  • "oatly.com이 스레드를 도입했는지, 게시물이 몇 개인지 알려줘."

  • "everlane.com의 페이스북 페이지를 찾아줘."

도구 및 입력

도구: map_meta_brand_presence

입력

유형

의미

company_domain

string

도메인만 있는 회사 도메인(예: shopify.com). 이 값 또는 핸들을 입력하세요. 도메인을 입력하면 액터가 전체 검색을 수행하고, 핸들을 입력하면 검색을 건너뜁니다.

company_name

string

선택 사항. 검색 정확도를 높이며, ID 게이트가 발견된 프로필을 대조하는 기준이 되므로 제공하면 잘못된 일치가 줄어듭니다.

handle

string

선택 사항. 앞에 @가 있거나 없는 인스타그램 핸들. 이 값을 제공하면 인스타그램 검색을 건너뛰고 스레드 핸들도 자동으로 제공되므로, 스레드 검색도 건너뜁니다.

platforms

array

매핑할 세 가지 Meta 표면 중 어떤 것을 선택할지 지정합니다. 기본값은 세 가지 모두입니다. 페이스북을 제외하는 것이 일반적입니다. 페이스북은 세 가지 중 가장 신뢰도가 낮고 비용이 많이 들기 때문입니다.

includeFollowerCounts

boolean

"true"(기본값)이면 프로필 페이지를 가져와 개수를 추출합니다. "false"로 설정하면 프로필 URL만 확인하는데, 이는 더 저렴하고 필요한 경우에만 사용하세요.

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 강화(enrichment) 액터 제품군을 구축합니다. 따라서 별도의 정리 단계 없이 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