This skill guides you on how to query and analyze the TikTok top selling product rankings via the FastMoss data source, helping cross-border e-commerce sellers identify hot-selling products across TikTok's global markets by day, week, or month.
Core Concepts
The TikTok Top Selling Ranking tracks the best-performing products on TikTok Shop across 15 global markets. It reveals which products are leading in sales volume, GMV, and growth rate over configurable time windows (daily, weekly, monthly). This is an essential tool for product scouting, trend analysis, and competitive intelligence in TikTok e-commerce.
Data scope: The ranking covers 15 TikTok Shop markets and supports three time granularities — day, week, and month — via the dateInfo parameter. Each product entry includes sales volume, GMV, growth rate, commission rate, shop information, category, and more.
dateInfo format is important:
- type:
"day"-> value:"2025-02-01"(YYYY-MM-DD) - type:
"week"-> value:"2025-18"(year-weekNumber) - type:
"month"-> value:"2025-02"(year-month)
Pagination: Results are paginated. Use page (page number, starting from 1) and pageSize (items per page, max 10, default 10) to navigate through the result set.
Parameter Guide
| Parameter | Type | Required | Description |
|---|---|---|---|
| region | string | Yes | Market region code (US, GB, MX, ES, DE, IT, FR, ID, VN, MY, TH, PH, BR, JP, SG) |
| dateInfo | object | Yes | Date specification with type (day/week/month) and value (see format above) |
| category | string | No | Category name in English, matched to TikTok category ID. Non-English input should be translated first |
| orderby | object | No | Sorting: field (units_sold/gmv/total_units_sold/total_gmv/growth_rate) + order (desc/asc). Default: desc |
| page | integer | No | Page number, default 1 |
| pageSize | integer | No | Items per page, max 10, default 10 |
Supported Markets
| Code | Market |
|---|---|
| US | United States |
| GB | United Kingdom |
| MX | Mexico |
| ES | Spain |
| DE | Germany |
| IT | Italy |
| FR | France |
| ID | Indonesia |
| VN | Vietnam |
| MY | Malaysia |
| TH | Thailand |
| PH | Philippines |
| BR | Brazil |
| JP | Japan |
| SG | Singapore |
Default market is US. Use US when the user does not specify a market.
How to call
- API endpoint：
POST /fastmoss/productRankTopSelling(For full parameters/responses/error codes seereferences/api.md） - Python script：
python scripts/fastmoss_product_rank_top_selling.py '<JSON 参数>' [--inline] - Cost constraints: This tool consumes compute; by default the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, page through, or change zip codes for continuous probing; if further retrieval is needed, first explain to the user that it will incur additional consumption.
Output strategy (script default behavior)：
- Alwayswrite the full response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-fastmoss-product-rank-top-selling-<timestamp>.json（<cwd>is the working directory when the script runs, in Claude Code this is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable, report an error) - Response body ≤ 8 KB: after saving to disk, print the full JSON to stdout
- Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, the length of the largest list field + the first 3 samples) - Add
--inlineto force full printing to stdout (also saved to disk)
Data reading suggestions: first look at the summary to determine whether it is sufficient; when specific fields are needed, prefer using jqorConvertFrom-Json to extract as needed from the saved json file, avoiding putting the entire JSON into the context.
Resolving authentication and compute issues
When the following abnormal situations occur, use references/onboarding.md to guide resolution:
Abnormal situations
- API Key not configured: the environment variable is not configured
LINKFOX_AGENT_API_KEY, nor isLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/plan expired/recharge required/please recharge", or content with similar meaning.
Usage Examples
1. Today's top selling products in the US (daily) Query the US market for a specific day to see which products lead in sales.
region: "US", dateInfo: {"type": "day", "value": "2026-04-15"}
2. Weekly top sellers in the UK Check the UK market for weekly best-performing products.
region: "GB", dateInfo: {"type": "week", "value": "2026-15"}
3. Monthly GMV leaders in Southeast Asia Scout the Indonesian market for monthly top sellers sorted by GMV.
region: "ID", dateInfo: {"type": "month", "value": "2026-03"}, orderby: {"field": "gmv", "order": "desc"}
4. Category-specific ranking Find top selling products in a specific category.
region: "US", dateInfo: {"type": "day", "value": "2026-04-15"}, category: "Beauty"
Data Fields (Response)
| Field | API Name | Description |
|---|---|---|
| Product Title | title | Name of the product |
| Product ID | productId | Unique product identifier |
| Region | region | Market region code |
| Price | price | Product price |
| Min Price | minPrice | Lowest price; optional and present only for price-range products |
| Max Price | maxPrice | Highest price; optional and present only for price-range products |
| Currency | currency | Currency symbol or label returned by the API |
| Total Sales | totalSaleCnt | Total units sold |
| 1-Day Sales | totalSale1dCnt | Units sold in the last 1 day (when dateType=day) |
| 7-Day Sales | totalSale7dCnt | Units sold in the last 7 days (when dateType=week) |
| 30-Day Sales | totalSale30dCnt | Units sold in the last 30 days (when dateType=month) |
| Total GMV | totalSaleGmvAmt | Total gross merchandise value |
| 1-Day GMV | totalSaleGmv1dAmt | GMV in the last 1 day (when dateType=day) |
| 7-Day GMV | totalSaleGmv7dAmt | GMV in the last 7 days (when dateType=week) |
| 30-Day GMV | totalSaleGmv30dAmt | GMV in the last 30 days (when dateType=month) |
| Growth Rate | growthRate | Sales growth rate (percentage) |
| Shop Name | shopName | Name of the seller's shop |
| Shop Total Units Sold | shopTotalUnitsSold | Total units sold by the shop |
| Shop Seller ID | shopSellerId | Unique shop seller identifier |
| Category Name | categoryName | Product category |
| Category IDs | categoryIds | Category ID path from level 1 to level 3 |
| Commission Rate | productCommissionRate | Commission rate in basis points (1000 = 10%) |
| Image URL | imageUrl | Product image URL |
| Cover URLs | coverUrl | Product cover image URL list |
| Shop Avatar | shopAvatar | Shop avatar URL |
| Source Tool | sourceTool | Source tool identifier |
| Source Type | sourceType | Product source type |
| Delisted Status | offShelvesText | Delisted indicator ("是" = delisted, "否" = active) |
Top-level responses include errcode, errmsg, page, pageSize, total, products, columns, type, and costTime. Some response variants may also include costToken, matchedCategoryIdPath, or matchedCategoryNamePath; consumers should treat these as optional.
Display Rules
- Present data only: Show query results in clear tables without subjective business advice
- Growth rate: Growth rate is in percentage -- show with % sign
- Commission rate: Commission rate is in basis points (1000 = 10%) -- convert to percentage for display
- Currency awareness: Always display currency alongside prices since different markets use different currencies
- dateInfo format: Validate and remind users of the correct format for the selected time granularity
- Delisted status:
offShelvesTextvalue "是" means delisted, "否" means active -- clarify this for users
Important Limitations
- dateInfo is mandatory: Both
typeandvaluemust be provided with specific format requirements - No keyword search: This tool does NOT support keyword search (use linkfox-fastmoss-product-search for that)
- Max 10 items per page: The
pageSizeparameter cannot exceed 10 - Data delay: Data has T+1 statistical delay
User Expression & Scenario Quick Reference
Applicable -- TikTok top selling product rankings and trend analysis:
| User Says | Scenario |
|---|---|
| "What are the top selling products on TikTok" | Top selling ranking lookup |
| "TikTok bestsellers this week", "hot products on TikTok Shop" | Weekly/daily ranking query |
| "TikTok GMV ranking", "highest revenue products on TikTok" | GMV-based ranking |
| "TikTok category hot sellers", "top selling beauty products on TikTok" | Category-specific ranking |
| "TikTok weekly product report", "monthly top sellers" | Time-dimension analysis |
| "FastMoss top selling", "FastMoss ranking data" | Direct data source reference |
| "Which products are growing fastest on TikTok" | Growth rate sorted ranking |
Not applicable -- Needs beyond TikTok top selling rankings:
- Amazon product research or ABA keyword data
- TikTok advertising / ad campaign management
- TikTok content creation or video editing
- Product reviews or listing copywriting
- TikTok product keyword search (use linkfox-fastmoss-product-search instead)
- Profit margin calculations or pricing strategy
Boundary judgment: When users say "product research" or "what's selling well", if the context clearly involves TikTok Shop or TikTok e-commerce rankings, this skill applies. If they are asking about Amazon, Shopify, or other platforms, it does not apply. If they want to search products by keyword rather than browse rankings, use linkfox-fastmoss-product-search instead.
Compute consumption rules
Consumes 11 compute.
Users pay fees due to compute consumption. Please fully assess: when this skill needs to be called frequently, or when the user has insufficient expectation of compute consumption, be sure to remind the user and let the user decide whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- Anything you believe could be improved
Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.
For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.