Vee3

tiktok.user_videos

List videos posted by a TikTok user. Provide either user_id or unique_id, not both. Set latest to true for newest posts or false for top posts. Pass cursor from a previous response to fetch the next page.

Cost = 3 tokens.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of items to return (max 30).
`cursor`	No	Pagination cursor from a previous response.
`latest`	No	When true, return latest videos. When false, return top videos.
`user_id`	No	TikTok numeric user id.
`unique_id`	No	TikTok unique id (username).

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.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals key behaviors: mutual exclusivity of user_id/unique_id, the latest/top mode switch, pagination via cursor, and the cost of 3 tokens. It does not mention rate limits or authorization requirements, but for a read-only list operation, it is fairly transparent.

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?

The description is compact and well-structured: a clear opening sentence, followed by three concise usage instructions, and a cost note. Every sentence earns its place with no wasted words.

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?

Given the tool's simplicity and the presence of an output schema, the description adequately covers the essential usage: how to specify the user, choose between latest/top, and paginate. It omits mention of the count parameter, but that is documented in the schema, and the main usage paths are all covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter described, so the baseline is 3. The description adds value by explicitly stating 'not both' for user_id and unique_id, which is a constraint not captured in the schema. The rest of the parameter hints (latest, cursor) largely repeat schema descriptions but are still helpful.

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 clearly states the tool's function as 'List videos posted by a TikTok user' with a specific verb and resource. It distinguishes from sibling tools like tiktok.user_followers, tiktok.user_info, and tiktok.user_reposts by focusing specifically on the user's video feed.

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?

Provides clear usage context: instructs to provide either user_id or unique_id (not both), explains latest vs. top posts, and mentions cursor for pagination. However, it does not explicitly mention alternative tools or when not to use this tool, so it falls short of a 5.

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.