Vee3

tiktok.user_following

List accounts a TikTok user follows. Requires user_id. Pass cursor from a previous response to fetch the next page.

Cost = 2 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of items to return (max 200).
`cursor`	No	Pagination cursor from a previous response.
`user_id`	Yes	TikTok numeric user id.

Output Schema

TableJSON Schema

Name	Required	Description
`msg`	No	Upstream status message.
`code`	No	Upstream status code (0 = success).
`data`	No	Capability-specific payload from the upstream provider.
`processed_time`	No	Upstream processing time in seconds.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 3, 2026

changedOutput schema / properties / processed_time / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

First observedJun 18, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses pagination behavior and cost, but does not mention rate limits, auth requirements, or what 'accounts' includes in the response. It's adequate but not rich.

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?

Two concise sentences plus a cost line. Front-loaded with the core purpose, and every sentence serves a purpose: what, required param, pagination, cost. No fluff.

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?

The tool is simple, has an output schema (so return values are covered), and the description covers the essential usage details (pagination, cost). It could mention rate limits or clarifying the 'accounts' type, but it's reasonably complete for a listing 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 coverage is 100%, so the schema already documents all three parameters. The description adds 'Requires user_id' and reiterates cursor usage, which adds marginal value but does not go beyond the schema—hence the baseline score of 3.

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 states a specific verb and resource: 'List accounts a TikTok user follows.' This clearly distinguishes it from sibling tools like user_followers (which lists followers) and user_info (which gets a user's own info).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: requires user_id and explains pagination via cursor. It does not explicitly name alternatives, but the phrase 'a user follows' makes the use case unambiguous compared to sibling tools like tiktok.user_followers.

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

All Vee3 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.