Resolve a TikTok handle or company domain to a brand's official TikTok account and return its public profile stats as one flat, Clay-ready row.
One tool, map_tiktok_brand_presence — pass a handle (primary, cheapest/most reliable) and/or a bare company_domain to find the handle, plus optional company_name to sharpen search and identity-check.
Returns profile data: follower, following, like and video counts, verification status, display name, bio and outgoing bio link, in a single flat row.
Discovery + identity gating: finds a brand's handle from a domain when you don't have one, and reports a guessed account that fails the identity check as identity_mismatch with no counts rather than handing back someone else's profile.
Honest data caveats: flags counts that TikTok rounds above roughly ten thousand.
Status vocabulary per row: ok, not_found, not_extractable, blocked, identity_mismatch, skipped — read _status first, and note false (looked, answer is no) is never interchangeable with null (couldn't look).
Cost/behavior controls: includeFollowerCounts=false for a cheaper URL-only resolve needing no proxy, skipCache=true to force a fresh fetch (default caches successful lookups 7 days), escalateOnBlock=true to retry a blocked fetch once over residential, and max_charge_usd to cap per-call spend.
Read-only, open-world, idempotent, non-destructive; requires an APIFY_TOKEN and consumes Apify credits per call on a pay-per-event basis.
Provides tools for resolving a TikTok handle or company domain to a brand's official TikTok account, returning profile details such as follower counts, verification status, bio, and outbound link.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-tiktok-brand-presence-mapper How many TikTok followers does Gymshark have?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Mamba Labs TikTok Brand Presence Mapper actor on Apify.
Resolve a TikTok handle or a company domain to the brand account with follower, like and video counts.
Resolve a TikTok handle, or a company domain, to that brand's official TikTok account. Returns follower, following, like and video counts, verification status, display name, bio and the account's outbound bio link, as one flat Clay ready row. Counts above roughly ten thousand are rounded by TikTok and the row flags that. A guessed account that fails the identity check is reported as identity_mismatch with no counts rather than being returned as the company's. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
Related MCP server: Company Identity Resolver MCP Server
Add this to your MCP client configuration:
{
"mcpServers": {
"mamba-tiktok-brand-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-tiktok-brand-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Node.js 18 or newer
An Apify API token from console.apify.com/account/integrations
The actor is pay per event and consumes Apify credits per call. Pricing is on the actor page.
"How many TikTok followers does Gymshark have?"
"Find the TikTok account for allbirds.com and tell me if it is verified."
"Check whether patagonia.com has a TikTok presence at all."
Tool: map_tiktok_brand_presence
Input | Type | Meaning |
| string | The TikTok handle, with or without the leading @, for example shopify. This is the PRIMARY input: only 4 of 14 B2B homepages declare a TikTok link, so |
| string | Bare company domain, for example shopify.com. Used to FIND the handle when you do not have one, and to identity check a handle that discovery guessed. |
| string | Optional. Improves search accuracy and is what the identity gate checks a discovered account against. |
| boolean | 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 need |
| boolean | 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 compatibi |
| boolean | TikTok answers most requests over cheap datacenter routing and blocks a minority with a bot detection page. When "true" (default) a blocked fetch is r |
| 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. |
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 |
| fetched and parsed, the value is there |
| we looked and there is no such profile |
| the profile exists and the value is not on the wire to us |
| the platform refused us, worth retrying later |
| we found a real profile and it belongs to someone else |
| 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.
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 |
| $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
| $0.004 on the Free plan, down to $0.0028 on higher Apify plans | Once per company for which the discovery cascade completed and a non degraded row was produced, whether or not a TikTok profile was found. Does not fire on a degraded row, because on a degraded row no discovery was performed. |
| $0.003 on the Free plan, down to $0.0021 on higher Apify plans | Once per company whose candidate TikTok 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. |
| $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.
apify.com/mambalabs/tiktok-brand-presence-mapper
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
MIT
Resolve a TikTok handle, or a company domain, to that brand's official TikTok account. Returns follower, following, like and video counts, verification status, display name, bio and the account's outbound bio link, as one flat Clay ready row. Counts above roughly ten thousand are rounded by TikTok and the row flags that. A guessed account that fails the identity check is reported as identity_mismatch with no counts rather than being returned as the company's, and a brand with no TikTok account reports tiktok_status not_found. Read tiktok_status before any count. Use it to look up one known brand per call; it does not search TikTok, list or read videos, or compare accounts, so pair it with the sibling presence mappers for other platforms. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | No | The TikTok handle, with or without the leading @, for example shopify. This is the PRIMARY input: only 4 of 14 B2B homepages declare a TikTok link, so supplying the handle is both cheaper and far more reliable than asking the actor to find it. | |
| skipCache | No | 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. | |
| company_name | No | Optional. Improves search accuracy and is what the identity gate checks a discovered account against. | |
| company_domain | No | Bare company domain, for example shopify.com. Used to FIND the handle when you do not have one, and to identity check a handle that discovery guessed. Supplying both is the best case. | |
| max_charge_usd | No | 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. | |
| escalateOnBlock | No | TikTok answers most requests over cheap datacenter routing and blocks a minority with a bot detection page. When "true" (default) a blocked fetch is retried once over residential, which recovers most of them at a higher cost per recovered row. Set "false" to accept the block and return status blocked. Sent as a string for Clay compatibility. | |
| includeFollowerCounts | No | 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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description carries rich behavior beyond annotations — count rounding above ~10k, identity_mismatch and tiktok_status not_found outcomes, the 'read tiktok_status before any count' ordering rule, APIFY_TOKEN requirement and per-call Apify credit consumption. However, it asserts 'Read only' while the annotations declare readOnlyHint=false, a direct conflict on the tool's mutation profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Long but dense and front-loaded: the core resolution behavior and return shape come first, then failure modes, then cost/auth caveats. Every sentence carries distinct operational information, though the single paragraph is heavier than strictly needed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description compensates by describing the returned flat row, its status fields, and the failure statuses. It also covers auth, cost, and caching behavior, so an agent has everything required to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and all seven parameters carry detailed, self-explanatory docs (including the handle-vs-domain primary-input guidance and the Clay string-serialization note). The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Resolve a TikTok handle, or a company domain, to that brand's official TikTok account') and enumerates exactly what comes back (follower/following/like/video counts, verification, display name, bio, outbound link). An agent knows precisely what this tool does and what it produces without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit when-to-use ('look up one known brand per call') and explicit when-not ('does not search TikTok, list or read videos, or compare accounts'), plus a routing hint to pair it with sibling presence mappers for other platforms. No sibling tools are registered here, but the boundary is still drawn clearly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.1map_tiktok_brand_presence2 fields changedInput schema / additionalPropertiesRemoved value: -falseInput schema / properties / max_charge_usdAdded 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"
+}v1.0.0map_tiktok_brand_presenceScored across 1 tool
Only one tool exists, so there is no possibility of misselection or overlap with sibling tools on this server. Its scope (resolve one known brand handle/domain to a TikTok account) is stated explicitly, including what it does not do.
The single tool follows a clear verb_noun snake_case pattern (map_tiktok_brand_presence) and is namespaced by platform, which would remain predictable if sibling presence mappers were added.
One tool is on the thin side for a server, though it is a focused, well-specified single-purpose utility rather than a trivial stub. It does one job (one brand lookup per call) and the description openly defers multi-brand, search and video operations to sibling mappers.
Within its declared scope the surface is complete: it returns identity status (tiktok_status, identity_mismatch) plus counts, bio and link, with clear failure semantics. Gaps are deliberate and documented (no batch lookups, no other platforms, no video data), so agents know to pair it with sibling servers.
Public TikTok profiles, videos, comments and keyword search as JSON. No developer account.
TikTok profiles, video stats and transcripts by handle or URL. No login. Pay per result.
Public data from Douyin, Xiaohongshu, Bilibili, Weibo, TikTok and 20+ platforms as unified JSON
Get social media data from Instagram and TikTok: profiles, posts, videos, comments, and more.
