mcp-tiktok-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_tiktok_brand_presenceA | 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. |
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
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.