This skill fetches the full profile of a single TikTok Shop store (seller) by its sellerId, helping cross-border sellers and marketers deep-dive one store's performance — sales, multi-period GMV, followers, ratings, fulfillment, and influencer/video/livestream reach.
Core Concepts
EchoTik is a TikTok Shop analytics platform. This tool returns one store's complete detail object: total and incremental (1d/7d/30d/90d) sales volume and GMV, followers, rating, reviews, positive-feedback / response / delivery rates, product counts, price range, categories, and promoting-influencer / video / livestream counts.
Where to get a sellerId: This skill requires a store's sellerId. Obtain it from the EchoTik TikTok Seller Search skill (linkfox-echotik-list-seller), which lists and filters TikTok Shop stores by region, category, GMV, trend, and store type.
Listing date: firstCrawlDt uses a compact integer format YYYYMMDD (e.g. 20240504 for May 4, 2024).
Data Fields
The response is a flat store object (top level also carries errcode, errmsg, costToken, columns, type).
| Field | Description |
|---|---|
| sellerId | Store ID |
| sellerName | Store name |
| sellerLink | Store link |
| coverUrl | Store cover image URL |
| region | Marketplace code |
| categoryId / categoryL2Id / categoryL3Id | Level-1 / 2 / 3 category ID |
| totalSaleCnt | Total sales volume |
| totalSale1dCnt / 7dCnt / 30dCnt / 90dCnt | Sales volume (1d/7d/30d/90d, incremental) |
| totalSaleGmvAmt | Total GMV (revenue) |
| totalSaleGmv1dAmt / 7dAmt / 30dAmt / 90dAmt | GMV (1d/7d/30d/90d, incremental) |
| followersCount | Follower count |
| rating | Store rating |
| reviewCount | Review count |
| positiveFeedbackRate | Positive feedback rate |
| responseRate | Response rate |
| deliveryRate | Delivery rate |
| totalProductCnt | Historical product count (incl. delisted) |
| totalCrawlProductCnt | Current in-store product count |
| spuAvgPrice | Avg SKU price in store |
| minPrice / maxPrice | Min / max price |
| totalIflCnt | Number of promoting influencers |
| totalVideoCnt | Number of promo videos |
| totalLiveCnt | Number of livestreams |
| salesFlagText | Main sales channel (video sales / livestream sales) |
| salesTrendFlagText | Sales trend (rising / falling / stable) |
| shopIdentityLabel | Store identity label (e.g. OFFICIAL SHOP) |
| shopTypeText | Brand store flag (yes / no) |
| fromFlagText | Local/cross-border flag (local / cross-border) |
| productCategoryList | Product categories (JSON string) |
| mostProductCategoryList | TOP1 product category (JSON string) |
| firstCrawlDt | Estimated listing time (YYYYMMDD) |
| userId | Influencer UID |
| sourceType | Source type (e.g. Tiktok) |
| sourceTool | Source tool |
| costToken | Tokens consumed |
| columns | Render column definitions (display metadata) |
| type | Render style (e.g. tableListWorkbenches) |
Parameter Guide
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| sellerId | string | Yes | - | TikTok Shop store ID. Obtain it from the Seller Search skill's results. Max length 1000 |
How to call
- API endpoint：
POST /echotik/sellerDetail(for full parameters/responses/error codes seereferences/api.md） - Python script：
python scripts/echotik_seller_detail.py '<JSON 参数>' [--inline] - Cost constraints: This tool consumes compute; within the same session, the same parameter combination is by default called only once, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, page through, or change zip codes to probe continuously; if further retrieval is needed, first explain to the user that it will incur additional consumption.
Output strategy (default script behavior)：
- Alwayswrite the complete response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-echotik-seller-detail-<timestamp>.json（<cwd>is the working directory when the script runs, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user task;writing to /tmp is prohibited, if the current directory is not writable, report an error) - Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
- Response body > 8 KB: after writing 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 written to disk)
Data reading recommendations: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.
Resolve authentication and compute issues
When the following abnormal situations occur, use references/onboarding.md to guide resolving the issues:
Abnormal situations
- API Key not configured: the environment variable is not configured with
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/package expired/recharge required/please recharge", or content with similar meaning.
Usage Examples
1. Fetch a store's full profile
{
"sellerId": "7495514739648989419"
}
2. Deep-dive a store found via Seller Search
先用店铺搜索列出美国GMV前列店铺，再查看其中 medicube US Store（sellerId 7495514739648989419）的完整详情
Display Rules
- Present a clear store profile: Show store name, region, seller link, cover image, and identity label (e.g. OFFICIAL SHOP)
- Sales & GMV granularity: Show total sales and total GMV; surface the multi-period breakdown (1d/7d/30d/90d) for both volume and GMV so the user sees momentum
- Store health metrics: Show followers, rating, review count, positive-feedback rate, response rate, and delivery rate together
- Store attributes: Show
fromFlagText(local/cross-border),salesFlagText(video/livestream sales),salesTrendFlagText(trend), andshopTypeText(brand store) for benchmarking - Reach metrics: Surface
totalIflCnt(influencers),totalVideoCnt(videos),totalLiveCnt(livestreams), and product counts - Store link: When
sellerLinkis present, surface it so the user can open the store - No secondary processing: Results are live queries, not stored in a database; secondary SQL/data processing is not available
Important Limitations
- sellerId required:
sellerIdis mandatory; obtain it from the EchoTik TikTok Seller Search skill (linkfox-echotik-list-seller) or a known store link/ID - Single store only: This returns one store's detail; to list and filter stores, use the Seller Search skill
- Listing date format:
firstCrawlDtusesYYYYMMDDintegers (e.g.20240504) - Category IDs:
categoryId/categoryL2Id/categoryL3Idare internal IDs, not human-readable names - Data real-time nature: Results are live queries, not stored in a database; secondary SQL/data processing is not available
User Expression & Scenario Quick Reference
Applicable — Deep-dive one TikTok Shop store's full profile:
| User Says | Scenario |
|---|---|
| "TikTok store details" / "TikTok store detail" | Fetch one store's full profile by sellerId |
| "view this TikTok store's data" | Deep-dive a store found via search |
| "analyze this TikTok store medicube" | Single-store performance analysis |
| "this TikTok store's GMV and follower count" | Store-level sales/GMV/follower metrics |
Not applicable — Needs beyond a single store detail:
- Listing or filtering TikTok Shop stores by region/GMV/trend (use EchoTik TikTok Seller Search)
- TikTok product search or product rankings (use EchoTik product search/rank skills)
- TikTok creator/influencer analytics (follower counts, engagement of creators)
- TikTok video performance analytics (views, likes on specific videos)
- Amazon, Shopee, or other non-TikTok platform data
- Store-level operations: order/logistics/ads management
Boundary judgment: When users say "analyze this store" or "view store details" with a known store (sellerId or store link), this skill applies. If they want to discover or list stores by criteria, use the Seller Search skill instead.
Compute consumption rules
Consumes 5 compute units.
Users will be charged for computing power consumption. Please fully assess: when this skill needs to be called frequently, or when users have insufficient expectations for the amount of computing power 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.