mcp-meta-brand-presence-mapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_meta_brand_presenceA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.