Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

tikTok-information-scraper

Search TikTok videos by keyword and collect related information from multiple results for research, monitoring, or content analysis.

Instructions

Search TikTok videos by keyword and collect related video information. Can collect multiple videos. Important: provide search keywords.

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": "tikTok-information-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
env_idsNoOne 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.
keywordYesTikTok keyword used to search for videos.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
getDataCountNoNumber of videos to scrape.
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

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and mostly does not meet it. It does not disclose that execution provisions an environment (implied by env_ids and run_timeout), that the environment is closed afterward by default, what video fields are returned, whether results are paginated, or any rate-limit/anti-bot constraints. 'Collect related video information' is too vague to tell an agent what it will receive.

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?

Three short sentences, front-loaded with the action before the constraint, with no filler. It is arguably too terse rather than bloated, but nothing wastes space.

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 scraping task with five parameters, no annotations, and no output schema, the description should explain what is returned and what the environment lifecycle implies for the caller. Neither is covered, leaving the agent to discover result shape and side effects at call time.

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 every parameter is already documented, including the is_cancel_close timeout interaction. The description adds no syntax, format, or defaulting detail beyond the schema, so the baseline of 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 and resource: search TikTok videos by keyword and collect related video information, plus the multi-video scope. It does not distinguish itself from the sibling tikTok-influencer-scraper, so an agent must infer the boundary, but the core action is unambiguous.

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?

The only guidance is a directive to supply search keywords, which is a restatement of the required parameter rather than a when-to-use rule. There is no statement of when to prefer this over tikTok-influencer-scraper or likes-counter, and no exclusions, so usage is only implied.

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