Skip to main content
Glama

tiktok

by com.scraptik

tiktok_creator_liked_videos

List videos a creator has publicly liked (only available when the account exposes its Likes tab). Use for taste/affinity analysis. Paginate with cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of items to return, <=35
cursorNoPagination cursor — pass the `cursor`/`max_cursor`/`has_more` value from a prior response.
expandNoReturn the full untrimmed payload. Default false = compact JSON.
user_idYes@username or numeric user_id

TDQS

A3.9/5.0
Behavior3/5

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

With empty annotations, the description carries full burden. It mentions pagination via cursor, but does not disclose other behavioral traits like authentication needs, rate limits, or side effects. For a read-only list tool, this is adequate but not comprehensive.

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 two sentences, front-loaded with purpose, and contains no fluff. Every sentence adds value.

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?

Given no output schema and 4 parameters, the description is minimally complete. It covers purpose, condition, and pagination, but lacks details about return value structure or what fields are in the response. Could be more complete.

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 baseline is 3. The description does not add meaning beyond what the schema already provides for parameters; it only reinforces cursor usage which is already documented.

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 verb 'List' and resource 'videos a creator has publicly liked', with a condition (only when Likes tab is exposed). It also distinguishes from siblings like tiktok_creator_videos (which lists the creator's own videos) by specifying it's for liked videos.

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 specifies a prerequisite (account exposes Likes tab) and a use case (taste/affinity analysis), but does not explicitly state when not to use it or provide alternatives. This is clear context for usage.

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

All tiktok toolsInspect
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.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a distinct data type or action (creator, video, comment, sound, hashtag, search, etc.) with no functional overlap. Agents can easily distinguish them based on their clear entity-action pairing.

Naming Consistency4/5

All tools follow a 'tiktok_' prefix and a consistent noun-first pattern (e.g., 'tiktok_creator_profile', 'tiktok_video_stats'), but there is a minor inconsistency between 'creator' and 'user' for the same entity (e.g., 'tiktok_user_stories' vs 'tiktok_creator_profile').

Tool Count4/5

At 19 tools, the count is slightly high but justified by the breadth of TikTok's public data surface (profiles, videos, comments, sounds, hashtags, searches, etc.). Each tool serves a specific purpose, and the set feels comprehensive rather than bloated.

Completeness4/5

The tool set covers most read-only operations for TikTok public data, including profiles, videos, comments, sounds, hashtags, and searches. Missing are direct trending feeds or aggregated analytics, but search capabilities compensate. No create/update/delete exists, which is expected for a data extraction server.

Resources