Skip to main content
Glama
TikTok Intelligence MCP Server

TikTok Intelligence MCP Server

by willowswt

spy_tiktok_brand_sponsors

Read-onlyIdempotent

Identify active DTC and SaaS brands sponsoring TikTok creators in a niche by scanning #ad posts, promo codes, and @brand tags, then resolve brand domains and contact emails.

Instructions

Detect active DTC & SaaS brands sponsoring TikTok creators in any niche (keyword) via #ad, #sponsored, #partner, promo codes, and @brand tags, resolving brand domains and contact emails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "spy_tiktok_brand_sponsors"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesNiche keyword (e.g. "protein powder", "ai tools", "skincare").
maxSponsorsNoMaximum sponsored campaign leads (1-15, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's burden is lighter and it does add real value: it discloses the detection methodology and that results are enriched with resolved brand domains and contact emails. It stops short of disclosing cost/latency behavior or what happens on an open-world scrape that finds no sponsors, which would matter given openWorldHint=true.

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 that leads with the verb and resource, then qualifies with niche and evidence signals. It is dense but every clause carries information; no filler or restated name/title.

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?

For a two-parameter read-only tool with no output schema, the description covers input scope, detection method, and the shape of returned data (brand domains, contact emails). Minor gaps remain around empty-result behavior and the effect of maxSponsors, but nothing essential to invoking it correctly is missing.

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 the schema already documents both 'keyword' (with examples) and 'maxSponsors' (range and default). The description only echoes that the keyword is a niche concept and adds no semantics for maxSponsors or the trade-off of raising it; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Detect') and resource ('active DTC & SaaS brands sponsoring TikTok creators'), plus the evidence signals used (#ad, #sponsored, promo codes, @brand tags) and the enrichment (brand domains, contact emails). It is clear what the tool returns, but it never distinguishes itself from the sibling 'find_tiktok_creator_emails', which also surfaces emails — an agent could plausibly confuse brand-contact discovery with creator-contact discovery.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative among the siblings (find_tiktok_creator_emails, search_tiktok_videos, mine_buyer_intent_comments). The hashtag/promo-code list describes the detection method rather than the conditions under which an agent should select this tool.

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