TikTok MCP Server

get_videos

Read-onlyIdempotent

Fetch a TikTok user's most recent public videos, returning id, caption, URL, and view count. Returns an empty list with a note if private or blocked.

Instructions

List a TikTok user's most recent public videos with id, caption, URL, and view count. Returns an empty list with a note if the account is private or TikTok blocks the request.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Maximum number of items to return (1-50).
`username`	Yes	TikTok handle, with or without the leading '@' (e.g. 'khaby.lame').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`videos`	Yes
`username`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description goes beyond them by disclosing the failure/edge-case behavior: an empty list with a note when the account is private or TikTok blocks the request, which is genuinely useful for interpreting results.

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 sentences, zero waste, front-loaded with what the tool returns before the edge-case note. Every sentence earns its place.

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?

An output schema exists, so the return shape need not be re-explained, and the description handles the private/blocked edge case well. It is nearly complete for calling the tool correctly; only the sibling-routing context is missing.

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 both parameters (count, username) are already documented in the schema. The description adds mild meaning via 'most recent' implying result ordering, but otherwise adds nothing beyond the structured fields. Baseline 3 applies.

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?

States a specific verb (list) and resource (a TikTok user's most recent public videos) plus the fields returned. It is clearly distinguishable from siblings like get_profile (profile data) and search_videos (keyword search) because it is scoped to one user's recent uploads.

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?

The phrasing 'List a TikTok user's most recent public videos' implies the usage context, but there is no explicit when-to-use guidance and no mention of the alternative search_videos sibling for broader discovery. Usage is inferable but not spelled out.

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

Deploy Server