Skip to main content
Glama
deenesjakoruzh
mambalabsdev

mcp-pinterest-brand-presence-mapper

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Pinterest Brand Presence Mapper MCP Server

Smithery Glama score npm version npm downloads license

MCP server for the Mamba Labs Pinterest Brand Presence Mapper actor on Apify.

Resolve a company domain to its Pinterest business account with exact follower, pin and board counts.

What it does

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.

Related MCP server: Company Social Presence Mapper MCP Server

Quick start

Add this to your MCP client configuration:

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

Prerequisites

The actor is pay per event and consumes Apify credits per call. Pricing is on the actor page.

Example prompts

  • "How many Pinterest followers and boards does brooklinen.com have?"

  • "Is chewy.com a verified merchant on Pinterest?"

  • "Compare Pinterest board counts across patagonia.com and article.com."

Tool and inputs

Tool: map_pinterest_brand_presence

Input

Type

Meaning

company_domain

string

Bare 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.

company_name

string

Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches.

handle

string

Optional. The Pinterest username from pinterest.com/. Supplying it skips discovery and, more importantly, skips the identity risk: Pinterest handles are rarely the domain stem.

includeFollowerCounts

boolean

Default true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy.

skipCache

boolean

Default false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.

max_charge_usd

number

Optional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Reading the output

Every row carries a per platform _status field, and it is the field to read first. The vocabulary is the same across the whole Mamba Labs social family:

Status

Meaning

ok

fetched and parsed, the value is there

not_found

we looked and there is no such profile

not_extractable

the profile exists and the value is not on the wire to us

blocked

the platform refused us, worth retrying later

identity_mismatch

we found a real profile and it belongs to someone else

skipped

you did not ask for this platform

false and null are never interchangeable. false means we looked and the answer is no. null means we could not look. If you filter for companies with no presence, filter on false, because null rows are unknown rather than absent.

Pricing

You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:

Event

Price per event (USD)

Fires when

apify-actor-start

$0.00005

Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).

company-checked

$0.0035 on the Free plan, down to $0.00245 on higher Apify plans

Once per company for which the discovery cascade completed and a non degraded row was produced, whether or not a Pinterest profile was found. Does not fire on a degraded row, because on a degraded row no discovery was performed.

profile-resolved

$0.003 on the Free plan, down to $0.0021 on higher Apify plans

Once per company whose candidate Pinterest URL passed the identity gate. Fires on the validation work, not on a populated count. A candidate dropped as an impersonator does not charge: the work was done and the honest answer is that there is no such profile.

follower-count-extracted

$0.0025 on the Free plan, down to $0.00175 on higher Apify plans

Once per company where a numeric follower count was read off the public page. Does not fire on not_extractable, blocked, identity_mismatch or url only runs.

The actor's Apify page carries the current prices. Running this server consumes Apify credits.

Full actor documentation

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

Mamba Labs GTM Suite

Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay ready output convention, so their rows join on company_domain with no cleaning step. Full fleet: apify.com/mambalabs

License

MIT

Available Tools

1 tool
map_pinterest_brand_presenceMap Pinterest Brand PresenceA
Idempotent

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
handleNoOptional. The Pinterest username from pinterest.com/<handle>. Supplying it skips discovery and, more importantly, skips the identity risk: Pinterest handles are rarely the domain stem.
skipCacheNoDefault false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
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.
max_charge_usdNoOptional spending cap for this call, in USD, passed to the actor as max_charge_usd. The run stops before any charge that would take it past this amount and keeps every row already charged. Leave empty to rely only on the maximum charge per run set on your Apify account.
includeFollowerCountsNoDefault true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy.

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare openWorldHint, idempotentHint and destructiveHint=false, but the description adds genuinely new behavioral facts: the paid-credit cost per call, the required APIFY_TOKEN, the identity-gate failure mode (identity_mismatch with no counts instead of a stranger's numbers), and that counts are real integers that can be summed. The 'Read only' phrasing sits in mild tension with readOnlyHint=false, but the description immediately qualifies it by disclosing the credit spend and external actor execution, which is the actual reason the tool is not flagged read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with the outcome and followed by interpretation, failure semantics, and cost/auth. The 'boards are curation effort' sentence is arguably interpretive filler for a parameter-oriented reader, but it earns its place by telling the agent how to weight the returned fields.

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?

With no output schema, the description carries the full burden and delivers: it enumerates the returned fields, the flat single-row shape, the caching behavior (in schema), the failure mode, the auth prerequisite, and the cost model. An agent has everything needed to call this correctly and to interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds interpretive value the schema does not: it explains why handle is more than a convenience (it skips the identity risk because Pinterest handles rarely match the domain stem) and why company_name reduces wrong matches via the identity gate. That rationale goes beyond the per-parameter text.

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 pair — 'Resolve a company domain to its Pinterest business account' — and then enumerates the exact return payload (follower, following, pin, board counts, claimed website, merchant status, last pin date). There are no sibling tools, but the scope is still unmistakable from the first clause alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the operating conditions clearly: domain vs. handle selects discovery vs. direct fetch, handle presence skips identity risk, and the call requires an APIFY_TOKEN and consumes credits. It does not state an explicit 'do not use this when…' case, but with no siblings to disambiguate against, the context is adequate rather than exhaustive.

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.1.1
    • Changedmap_pinterest_brand_presence4 fields changed
      • removedInput schema / additionalProperties
        Removed value: -false
      • changedInput schema / properties / includeFollowerCounts / description
        Previous value: -"When \"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."New value: +"Default true: the profile page is fetched and the follower counts are extracted. Set false to resolve the profile URL only, which is cheaper and needs no proxy."
      • addedInput schema / properties / max_charge_usd
        Added value: +{
+  "description": "Optional spending cap for this call, in USD, passed to the actor as max_charge_usd. The run stops before any charge that would take it past this amount and keeps every row already charged. Leave empty to rely only on the maximum charge per run set on your Apify account.",
+  "minimum": 0,
+  "type": "number"
+}
      • changedInput schema / properties / skipCache / description
        Previous value: -"When \"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."New value: +"Default false: a successful lookup is cached for seven days and reused. Set true to force a fresh fetch."
  2. 1 tool updatev1.0.0
    • First observedmap_pinterest_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.4/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers