Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok profile followers

tiktok_profile_followers_list
Read-onlyIdempotent

List followers of a TikTok profile by handle, using cursor pagination to retrieve complete follower lists.

Instructions

List followers of a TikTok profile by handle. Requires handle. Returns a list (use cursor when paginated).

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_profile_followers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoOptional flag for a smaller response with fewer fields.
cursorNoPagination cursor returned by a previous response.
handleYesRequired. TikTok handle whose followers should be listed.
userIdNoOptional TikTok user id to speed up the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the result is a list and that a cursor applies when paginated, which is modest but real context. It says nothing about rate limits, auth needs, or result size limits, so it does not go beyond a minimum.

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?

Two short sentences, front-loaded with the core action and with zero filler. It is efficient, though the parenthetical pagination note is close to circular ('use cursor when paginated') and could have carried more substance in the same space.

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

Completeness3/5

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

For a simple read-only list tool with a fully documented 7-param schema and no output schema, the description covers the essentials. However, it omits how the first cursor is obtained, any cap on results, and any differentiation from the closely named following/audience tools, leaving gaps an agent must resolve elsewhere.

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% across all 7 parameters, so the schema already explains handle, cursor, trim, userId, context, llm_model and conversation_id in detail. The description only restates handle and cursor, adding no format, default, or interaction meaning beyond the schema. 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 ('List followers of a TikTok profile by handle'), which clearly separates it from tiktok_profile_following_list and from the other platforms' follower tools by naming TikTok and followers. It stops short of explicitly naming a sibling it is not, so it lands at 4 rather than 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 usage statement is the precondition 'Requires `handle`', which the schema already marks required. There is no guidance on when to choose this over tiktok_profile_following_list, the audience/engagement aggregates, or the search variant, and no exclusions or prerequisites beyond the required param.

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

Deploy Server

Other Tools