Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

tikTok-influencer-scraper

Collect TikTok influencer follower data from a profile URL or username, with configurable record counts, to support audience research and outreach.

Instructions

Scrape and collect TikTok influencer follower data. Important: provide the influencer profile URL or username.

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": {
      "env_ids": "<env_ids>",
      "homeUrl": "<homeUrl>"
    },
    "name": "tikTok-influencer-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of follower records to scrape.
env_idsYesOne or more environment IDs where this task should run. If the user did not provide environment details (name, id, remark, serial number), prompt for them or offer to help create an environment.
homeUrlYesFull profile URL of the TikTok influencer. If the user provides only a username, you may assist by constructing the full URL (e.g. https://www.tiktok.com/@shou.time).
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
is_cancel_closeNoShould the environment be closed after the execution is completed? 0 means close, 1 means do not close. The default is 0. If you set it to 1, please set run_timeout to 0 to avoid automatic closing due to timeout.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about the browser/environment execution model, how long a scrape takes, rate limits, or account-login requirements. The only behavioral hints (environment closing, timeouts) live in the schema, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste; the core capability and the key input requirement are front-loaded in that order.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two required parameters, an environment-orchestration concept (env_ids), and no output schema or annotations, the description is too thin. It never explains what a follower record contains, how many are returned by default, or that an environment must exist before calling.

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 five parameters are already documented, establishing a baseline of 3. The description restates the homeUrl requirement (URL or username) but adds no format or constraint details beyond what the schema already says.

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 ('scrape and collect') and a specific resource ('TikTok influencer follower data'), which is enough for an agent to distinguish it from siblings like tikTok-information-scraper or tikTok-likes-counter. It does not explicitly contrast itself with those siblings, keeping it short of a 5.

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?

The only guidance is 'provide the influencer profile URL or username', which is a parameter reminder rather than a when-to-use rule. There is no statement of when this tool is preferable to the other TikTok tools, nor any prerequisites or exclusions.

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