mcp-pinterest-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. Required to run the Pinterest Brand Presence Mapper actor; each call consumes Apify credits. |
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_pinterest_brand_presenceA | Resolve a company domain to its Pinterest business account and return EXACT follower, following, pin and board counts, plus the claimed website, verified merchant status and last pin date, as one flat Clay ready row. Pinterest serves real integers, so these counts can be summed across a list. Board count is a better activity signal than followers for a consumer brand, because boards are curation effort. Pinterest handles are rarely the domain stem, so a guessed account that fails the identity check is reported as identity_mismatch with no counts rather than returning a stranger's numbers. 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 in the set, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single tool has one clearly stated job: domain -> Pinterest business account enrichment row.
The lone name 'map_pinterest_brand_presence' follows a clean verb_noun snake_case convention that matches the server's stated purpose. There is no competing convention to create inconsistency.
One tool is thin even for a narrowly scoped enrichment server; there is no companion for batch input, board-level detail, or verification retries. It is borderline rather than wrong, since the single tool does perform the entire advertised mapping.
For its stated purpose the tool covers identity resolution, the four counts, claim/merchant verification, and an explicit identity_mismatch failure mode, which is solid lifecycle coverage. Gaps remain: no board- or pin-level drilldown, no historical/trend data, and no batch or multi-domain input.