mcp-meta-brand-presence-mapper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
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.
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.
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.
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.