Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_user_following

Fetch the accounts a TikTok user follows by handle, with pagination via min_time and optional trimmed responses.

Instructions

tiktok: Following. GET /v1/tiktok/user/following. Scrapes accounts that a TikTok user follows 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

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>"
    },
    "name": "tiktok_user_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true to get a trimmed response
handleYesTikTok 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

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does deliver real behavioral detail: 1 credit on success, zero cost for errors, blocked/timed-out requests, invalid requests and cache hits, and conditional charging for empty results. That is meaningful operational context, though it omits rate limiting, auth requirements, and what a 'blocked' response looks like to the caller.

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 identity and endpoint are front-loaded in the first two fragments, and the cost information follows. The final charge sentence is somewhat verbose boilerplate with a conditional caveat, but it is not redundant enough to hurt readability.

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?

With no output schema, the description should describe the shape of the returned following list and how pagination actually works (min_time taken from a previous response). It covers cost semantics well but leaves the return value and pagination loop unexplained, which is a real gap for a list-scraping tool.

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 handle, trim and min_time are already documented in the schema, including the pagination hint for min_time. The description adds nothing about how these parameters affect the result, so the 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 ('Scrapes accounts that a TikTok user follows') plus the exact endpoint GET /v1/tiktok/user/following. The followed-accounts meaning is unambiguous against the tiktok_user_followers sibling, but the description never explicitly names that contrast, leaving the agent to infer it from the word 'following'.

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 only implied by the resource name; there is no statement of when to pick this over tiktok_user_followers or github_user_following, and no prerequisites such as whether a private account returns anything. The agent can infer the use case but gets no routing guidance.

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