Skip to main content
Glama

tiktok-scraper-video-downloader-api-mcp

Get Creator Followers

tiktok_user_followers
Read-onlyIdempotent

Get paginated follower accounts of a TikTok creator (up to 200 per call, 1 credit per follower).

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": {
      "user_id": "<user_id>"
    },
    "name": "tiktok_user_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoPagination timestamp cursor ("0" for first page)0
countNoFollowers per page (max 200)
sec_uidNoOptional creator secUid
user_idYesNumeric TikTok user_id (resolve via tiktok_user_info first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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). The description adds value the annotations do not: a hard 200-per-call ceiling and a per-follower credit cost, which directly affects how an agent should page and budget.

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 wasted clauses; the page size and cost constraints are appended compactly. Nothing is buried or redundant, though it could be slightly more explicit about what a page of accounts contains.

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 read-only paginated list tool whose annotations carry safety and whose schema carries all parameters, this is close to sufficient. The cursor-based pagination story is complete; the only gap is that the returned follower account fields are not characterized, which matters slightly given no output schema exists.

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 coverage is 100%, so the schema already documents all four parameters including the time cursor and count default. The description only reinforces the 200 cap already present in the count field, adding no syntax or format detail beyond the schema, so 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 and resource: "Get paginated follower accounts of a TikTok creator." An agent can distinguish this from the following-list sibling because followers versus following is explicit in the wording, though the sibling is never named as a contrast point.

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?

Usage is implied rather than stated: it must be called for a creator whose user_id is known, and the schema itself nudges toward resolving via tiktok_user_info first. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives such as tiktok_user_following are named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources