Skip to main content
Glama
TikTok Intelligence MCP Server

TikTok Intelligence MCP Server

by willowswt

find_tiktok_creator_emails

Read-onlyIdempotent

Find TikTok micro-influencers, UGC creators, and Shop affiliates by keyword or @handle, then crawl bio links to extract verified emails, Calendly links, and social profiles.

Instructions

Discover TikTok micro-influencers, UGC creators, and Shop affiliates in any niche (keyword or handle) and crawl external bio links (Linktree, Beacons, storefronts) to extract verified emails, Calendly links, and socials.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tiktok_creator_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoOptional specific TikTok @username to enrich.
keywordNoCreator niche keyword (e.g. "ugc creator", "fitness coach").
maxCreatorsNoMaximum creators to enrich (1-12, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety bar is lower, and the description still adds real behavior: it follows external bio links (Linktree, Beacons, storefronts) rather than only reading TikTok, and returns verified emails, Calendly links, and socials. It does not disclose crawl latency, failure behavior when no email is found, or how 'verified' is determined, which keeps it below a 5.

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?

A single front-loaded sentence with no filler; the discovery scope comes first and the extraction outcome second. It is dense to the point of being a run-on, which slightly hurts scannability, but no clause is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully names the returned artifacts (emails, Calendly links, socials), and annotations carry the safety profile. For a three-optional-parameter tool it is close to complete, though it omits what happens on empty results and any cost/time implications of crawling up to 12 creators.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented in the schema, making 3 the baseline. The description reinforces that `keyword` scopes by niche and `handle` targets enrichment, but adds no syntax, format, or behavior detail for `maxCreators` beyond what the schema states.

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?

Specific verb ('Discover') plus a precisely scoped resource (TikTok micro-influencers, UGC creators, Shop affiliates) and an explicit secondary action (crawl bio links to extract emails). The sibling set covers sounds, videos, brand sponsors, hooks, and comments, so this creator-contact-enrichment purpose is clearly differentiated without opening any schema.

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

Usage Guidelines3/5

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

It signals the two entry modes ("in any niche (`keyword` or `handle`)"), which implies how to invoke it for prospecting versus enrichment, but it never states when to choose this over a sibling tool or when it is inappropriate (e.g., single known creator vs. broad discovery). Usage is inferable rather than instructed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.