mcp-tiktok-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_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. 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 a single tool, there is no possibility of overlap or confusion between different operations.
The tool name 'map_tiktok_brand_presence' is clear, descriptive, and follows a consistent verb_noun pattern; no inconsistency issues with a single tool.
Having only one tool makes the surface feel thin for a server that ostensibly aims to map brand presence on TikTok, though it might be acceptable if the scope is extremely narrow. It falls into the borderline category.
The tool only resolves a single brand to its TikTok account and returns basic stats. There are significant gaps—no search, listing, comparison, or update capabilities—which would force agents to rely on external workarounds for related tasks.