Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_user_followers

Retrieve followers for a TikTok account using its handle or user ID, with pagination and optional trimmed responses, to support audience analysis.

Instructions

tiktok: Followers. GET /v1/tiktok/user/followers. Scrapes followers of a TikTok account Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_user_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true to get a trimmed response
handleNoTikTok handle
user_idNoTikTok handle or user id. Prefer handle.
min_timeNoUsed to paginate. Get 'min_time' from previous response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a meaningful cost model: 1 credit only on success, free for errors, blocked or timed-out requests, invalid requests, and cache hits. It says nothing about authentication, rate limits, response shape, or what happens when neither handle nor user_id is supplied, even though required is empty.

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?

The purpose and endpoint are front-loaded in the first two short sentences, followed by the cost note. The final sentence, 'A not-found or empty result is charged only where that operation's published cost says so'., is hedged and vague, which is a waste of words, but the overall size is reasonable.

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?

No annotations and no output schema exist, so the description must explain more. It does not say how to pick between handle and user_id, what the response contains, or how min_time pagination works end-to-end. It is adequate for a scraping endpoint but leaves real gaps.

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 description does not need to re-document the parameters, and it adds no syntax, format, or constraint details beyond what the schema already provides. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 verb and resource: 'Scrapes followers of a TikTok account', plus the endpoint GET /v1/tiktok/user/followers. It does not explicitly distinguish itself from the obvious sibling tiktok_user_following, so an agent must infer that from the name alone.

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 guidance on when to use this tool instead of tiktok_user_following or tiktok_profile, and no prerequisites are stated. The only implied usage cue is the min_time pagination note carried over from the schema, which is behavioral rather than a routing rule.

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