Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

tikTok-likes-counter

Automates TikTok account activity by browsing home feed videos and liking them with configurable delays and video counts. Set like mode and browse count per environment to simulate natural engagement.

Instructions

Activate TikTok accounts: automatically browse home feed videos and like them.

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>"
    },
    "name": "tikTok-likes-counter"
  }
}

Input Schema

NameRequiredDescriptionDefault
isLikeNoWhether to like videos.random
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.
likeDelayNoDelay before liking a video, in milliseconds. Example ["2000", "3000"] means a random delay between 2 and 3 seconds.
playCountNoNumber of videos to browse.
run_timeoutNoOverall process timeout in seconds. The environment will be closed automatically after this period.
scrollDelayNoDelay before scrolling to the next video, in milliseconds. Example ["4000", "8000"] means a random delay between 4 and 8 seconds.
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?

With no annotations, the description carries the full behavioral burden, and it discloses only that it browses the feed and likes videos. It says nothing about the side effects of performing real likes, whether actions are reversible, what credentials or account state are required, or how results are reported. The timeout and environment-closing behavior appear only in the schema, not as context in 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.

Conciseness4/5

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

It is a single front-loaded sentence with no filler, which makes the core action immediately clear. The brevity is efficient but leaves no room for usage or behavioral context, so it is tight rather than genuinely well-structured.

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 seven-parameter, long-running automation task with no annotations and no output schema, the definition is under-described. It does not explain what the run produces, how the environment lifecycle interacts with run_timeout, or what an agent should expect on completion. The schema covers the inputs, but the description leaves the operational picture incomplete.

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%, including the enum meanings for isLike and is_cancel_close, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond what is already structured. Baseline 3 applies when the input schema is fully documented.

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?

The description names a specific resource and action: activating TikTok accounts by browsing the home feed and liking videos. An agent can tell it performs real engagement on accounts rather than scraping. It does not distinguish itself from the sibling TikTok scrapers, and the tool name ('likes-counter') is slightly at odds with the described behavior of liking videos.

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 stated when-to-use guidance, no prerequisites, and no mention of the sibling TikTok scraper tools as alternatives. The only implied usage ('activate TikTok accounts') is inferred, not explicit. Nothing tells an agent under what conditions this tool is the right choice.

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