Nexscope TikTok Seller Detail
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
Nexscope 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 Nexscope TikTok Seller Search results, 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 store object is inside platform data, alongside business costToken, columns, and type. The outer code / msg carry platform status.
| 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 / live stream) |
| salesTrendFlagText |
Sales trend (rising / declining / 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 (see references/api.md for full parameters/response/error codes)
- Python Script:
python scripts/tiktok_seller_detail.py '<JSON parameters>' [--inline]
- Cost constraint: This tool consumes credits; the same parameter combination in the same session is called only once by default, with 24h local caching in the script. On failure/empty results, do not automatically retry with different keywords, pagination, or filter changes; inform the user before making additional queries.
Output strategy (default script behavior):
- Always write the full response to
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-echotik-seller-detail-<timestamp>.json (<cwd> is the working directory at script execution time, i.e., the current project directory in Claude Code; <session> is taken from the SESSION_ID environment variable, auto-grouped by user task; do not write to /tmp, error if the current directory is not writable)
- Response body <= 8 KB: print the full JSON to stdout after writing to disk
- Response body > 8 KB: stdout only outputs a summary (top-level fields, common counts like
total/costToken, length of the largest list field + first 3 samples)
- Add
--inline to force full output to stdout (still writes to disk)
Data reading tip: Check the summary first to see if sufficient; for specific fields, prefer using jq or ConvertFrom-Json to extract from the saved JSON file on demand, avoiding loading the entire JSON into context.
Response handling
For the research HTTP response, require a numeric outer code equal to 0 before using data. Nonzero codes are platform failures; display outer msg without interpreting its wording as a retry instruction. Nexscope preserves upstream messages and translates Chinese to English; successful responses may have msg: null. HTTP 200 alone and nested business code / status do not replace the platform check. See references/api.md for response paths and task-specific states.
Authentication
Set NEXSCOPE_API_KEY. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.
Usage Examples
1. Fetch a store's full profile
{
"sellerId": "7495514739648989419"
}
2. Deep-dive a store found via Seller Search
First use seller search to list top US stores by GMV, then view the full detail of 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/live driven), salesTrendFlagText (trend), and shopTypeText (brand store) for benchmarking
- Reach metrics: Surface
totalIflCnt (influencers), totalVideoCnt (videos), totalLiveCnt (livestreams), and product counts
- Store link: When
sellerLink is 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:
sellerId is mandatory; obtain it from seller search results 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:
firstCrawlDt uses YYYYMMDD integers (e.g. 20240504)
- Category IDs:
categoryId / categoryL2Id / categoryL3Id are 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 detail" / "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 medicube's TikTok store" |
Single-store performance analysis |
| "GMV and followers for this TikTok store" |
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 seller search)
- TikTok product search or product rankings (use 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 detail" 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.
API Key request rate
All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.
If an execution request returns HTTP 429 with outer code 13012, the request-rate allowance was exceeded. Honor the returned Retry-After before considering another request. Outer code 13013 means the concurrent-request limit was exceeded, not the rate limit; honor its Retry-After when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.
1---2name: ecommerce-tiktok-seller-detail3description: Query TikTok Shop store (seller) details, retrieving a complete store profile by sellerId with total sales, multi-period (1d/7d/30d/90d) sales and GMV, followers, rating, review count, positive feedback rate, delivery rate, response rate, in-store product count, promoting creator count, promotional video count, livestream count, price range, product categories, and estimated listing time. Trigger when users mention TikTok store detail, TikTok seller detail, TikTok store analysis, TikTok store data, TikTok store profile, TikTok Shop store detail, TikTok seller detail, Nexscope store profile. Even if the user does not explicitly mention "Nexscope" or "TikTok", trigger this skill whenever their need involves querying the full detail/profile of a specific TikTok Shop store (with a known sellerId).4metadata:5 source: https://skillmd.com/skills/nexscope-ai/ecommerce-tiktok-seller-detail6---78# Nexscope TikTok Seller Detail910This 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.1112## Core Concepts1314Nexscope 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.1516**Where to get a `sellerId`**: This skill requires a store's `sellerId`. Obtain it from the Nexscope TikTok Seller Search results, which lists and filters TikTok Shop stores by region, category, GMV, trend, and store type.1718**Listing date**: `firstCrawlDt` uses a compact integer format `YYYYMMDD` (e.g. `20240504` for May 4, 2024).1920## Data Fields2122The store object is inside platform `data`, alongside business `costToken`, `columns`, and `type`. The outer `code` / `msg` carry platform status.2324| Field | Description |25|-------|-------------|26| sellerId | Store ID |27| sellerName | Store name |28| sellerLink | Store link |29| coverUrl | Store cover image URL |30| region | Marketplace code |31| categoryId / categoryL2Id / categoryL3Id | Level-1 / 2 / 3 category ID |32| totalSaleCnt | Total sales volume |33| totalSale1dCnt / 7dCnt / 30dCnt / 90dCnt | Sales volume (1d/7d/30d/90d, incremental) |34| totalSaleGmvAmt | Total GMV (revenue) |35| totalSaleGmv1dAmt / 7dAmt / 30dAmt / 90dAmt | GMV (1d/7d/30d/90d, incremental) |36| followersCount | Follower count |37| rating | Store rating |38| reviewCount | Review count |39| positiveFeedbackRate | Positive feedback rate |40| responseRate | Response rate |41| deliveryRate | Delivery rate |42| totalProductCnt | Historical product count (incl. delisted) |43| totalCrawlProductCnt | Current in-store product count |44| spuAvgPrice | Avg SKU price in store |45| minPrice / maxPrice | Min / max price |46| totalIflCnt | Number of promoting influencers |47| totalVideoCnt | Number of promo videos |48| totalLiveCnt | Number of livestreams |49| salesFlagText | Main sales channel (video / live stream) |50| salesTrendFlagText | Sales trend (rising / declining / stable) |51| shopIdentityLabel | Store identity label (e.g. OFFICIAL SHOP) |52| shopTypeText | Brand store flag (yes / no) |53| fromFlagText | Local/cross-border flag (local / cross-border) |54| productCategoryList | Product categories (JSON string) |55| mostProductCategoryList | TOP1 product category (JSON string) |56| firstCrawlDt | Estimated listing time (YYYYMMDD) |57| userId | Influencer UID |58| sourceType | Source type (e.g. Tiktok) |59| sourceTool | Source tool |60| costToken | Tokens consumed |61| columns | Render column definitions (display metadata) |62| type | Render style (e.g. tableListWorkbenches) |6364## Parameter Guide6566| Parameter | Type | Required | Default | Description |67|-----------|------|----------|---------|-------------|68| sellerId | string | Yes | - | TikTok Shop store ID. Obtain it from the Seller Search skill's results. Max length 1000 |6970## How to Call7172- **API Endpoint**: `POST /echotik/sellerDetail` (see `references/api.md` for full parameters/response/error codes)73- **Python Script**: `python scripts/tiktok_seller_detail.py '<JSON parameters>' [--inline]`74- **Cost constraint**: This tool consumes credits; the same parameter combination in the same session is called only once by default, with 24h local caching in the script. On failure/empty results, do not automatically retry with different keywords, pagination, or filter changes; inform the user before making additional queries.7576**Output strategy (default script behavior)**:77- **Always** write the full response to `<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-echotik-seller-detail-<timestamp>.json` (`<cwd>` is the working directory at script execution time, i.e., the current project directory in Claude Code; `<session>` is taken from the `SESSION_ID` environment variable, auto-grouped by user task; **do not write to /tmp**, error if the current directory is not writable)78- Response body <= 8 KB: print the full JSON to stdout after writing to disk79- Response body > 8 KB: stdout only outputs a summary (top-level fields, common counts like `total`/`costToken`, length of the largest list field + first 3 samples)80- Add `--inline` to force full output to stdout (still writes to disk)8182**Data reading tip**: Check the summary first to see if sufficient; for specific fields, prefer using `jq` or `ConvertFrom-Json` to extract from the saved JSON file on demand, avoiding loading the entire JSON into context.8384## Response handling8586For the research HTTP response, require a numeric outer `code` equal to `0` before using `data`. Nonzero codes are platform failures; display outer `msg` without interpreting its wording as a retry instruction. Nexscope preserves upstream messages and translates Chinese to English; successful responses may have `msg: null`. HTTP 200 alone and nested business `code` / `status` do not replace the platform check. See `references/api.md` for response paths and task-specific states.8788## Authentication8990Set `NEXSCOPE_API_KEY`. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.9192## Usage Examples9394**1. Fetch a store's full profile**95```json96{97 "sellerId": "7495514739648989419"98}99```100101**2. Deep-dive a store found via Seller Search**102```103First use seller search to list top US stores by GMV, then view the full detail of medicube US Store (sellerId 7495514739648989419)104```105106## Display Rules1071081. **Present a clear store profile**: Show store name, region, seller link, cover image, and identity label (e.g. OFFICIAL SHOP)1092. **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 momentum1103. **Store health metrics**: Show followers, rating, review count, positive-feedback rate, response rate, and delivery rate together1114. **Store attributes**: Show `fromFlagText` (local/cross-border), `salesFlagText` (video/live driven), `salesTrendFlagText` (trend), and `shopTypeText` (brand store) for benchmarking1125. **Reach metrics**: Surface `totalIflCnt` (influencers), `totalVideoCnt` (videos), `totalLiveCnt` (livestreams), and product counts1136. **Store link**: When `sellerLink` is present, surface it so the user can open the store1147. **No secondary processing**: Results are live queries, not stored in a database; secondary SQL/data processing is not available115116## Important Limitations1171181. **sellerId required**: `sellerId` is mandatory; obtain it from seller search results or a known store link/ID1192. **Single store only**: This returns one store's detail; to list and filter stores, use the seller search skill1203. **Listing date format**: `firstCrawlDt` uses `YYYYMMDD` integers (e.g. `20240504`)1214. **Category IDs**: `categoryId` / `categoryL2Id` / `categoryL3Id` are internal IDs, not human-readable names1225. **Data real-time nature**: Results are live queries, not stored in a database; secondary SQL/data processing is not available123124## User Expression & Scenario Quick Reference125126**Applicable** -- Deep-dive one TikTok Shop store's full profile:127128| User Says | Scenario |129|-----------|----------|130| "TikTok store detail" / "TikTok store detail" | Fetch one store's full profile by sellerId |131| "View this TikTok store's data" | Deep-dive a store found via search |132| "Analyze medicube's TikTok store" | Single-store performance analysis |133| "GMV and followers for this TikTok store" | Store-level sales/GMV/follower metrics |134135**Not applicable** -- Needs beyond a single store detail:136137- Listing or filtering TikTok Shop stores by region/GMV/trend (use seller search)138- TikTok product search or product rankings (use product search/rank skills)139- TikTok creator/influencer analytics (follower counts, engagement of creators)140- TikTok video performance analytics (views, likes on specific videos)141- Amazon, Shopee, or other non-TikTok platform data142- Store-level operations: order/logistics/ads management143144**Boundary judgment**: When users say "analyze this store" or "view store detail" 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.145146## API Key request rate147148All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.149150If an execution request returns HTTP 429 with outer code `13012`, the request-rate allowance was exceeded. Honor the returned `Retry-After` before considering another request. Outer code `13013` means the concurrent-request limit was exceeded, not the rate limit; honor its `Retry-After` when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.