Skip to main content
Glama

Get the accounts a TikTok user follows

tiktok_get_user_following
Read-onlyIdempotent

List the accounts a public TikTok user follows, by username, with each account’s username, nickname, bio, avatar and follower counts. Page through results with the cursor from the previous response's nextCursor. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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": {
      "uniqueId": "<uniqueId>",
      "count": "<count>"
    },
    "name": "tiktok_get_user_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–30). Defaults to 30.
cursorNoThe previous response's `nextCursor`, to fetch the next page. Omit it for the first page.
uniqueIdYesTikTok username, with or without @, or the profile link, for example "tiktok" or "https://www.tiktok.com/@tiktok".
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
      +  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / cacheOnly
      Added value: +{
      +  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/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 restates read-only but adds genuinely new context — the 1-credit-per-request cost and the pagination contract via nextCursor. It does not cover what happens for private/suspended accounts or rate limiting, which keeps it below a top score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Four short sentences, front-loaded with the resource and scope, followed by pagination, safety and cost. Every sentence carries distinct information — there is no filler or repetition of the title alone.

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 5-parameter, read-only list tool with full schema coverage and no output schema, the description covers purpose, pagination and cost well. The only gap is caching behavior (cacheOnly / cacheMaxAgeHours trade-offs), which lives entirely in the schema and is not hinted at here.

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 all five parameters (uniqueId, count, cursor, cacheOnly, cacheMaxAgeHours) are already documented in the schema, including formats and limits. The description only reinforces the cursor-to-nextCursor relationship and that uniqueId is a username; it adds nothing about count bounds or the two cache parameters, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'List the accounts a public TikTok user follows' — and immediately scopes the operation to public profiles. The direction of the relationship ('follows' rather than 'followers') is unambiguous, so an agent can distinguish it from the followers sibling without opening either schema.

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: the description explains how to page ('use the cursor from the previous response's nextCursor') and notes the data is public, which indirectly rules out private accounts. It never explicitly says when to pick this over tiktok_get_user or tiktok_get_user_followers, or what to do when a user is private.

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