Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

TikTok Intelligence ET: list Seller API

nexscope_data_et_list_seller
Read-only

TikTok Intelligence ET: list Seller API.

Input Schema

NameRequiredDescriptionDefault
regionYesarea. Optional values: US (United States), ID (Indonesia), TH (Thailand), PH (Philippines), MY (Malaysia), VN (Vietnam), GB (UK), MX (Mexico), SG (Singapore), SA (Saudi Arabia), BR (Brazil), ES (Spain), JP (Japan), DE (Germany), IT (Italy), FR (France)
pageNumNoPagination page number, starting from 1
fromFlagNoStore source: 1=local store, 2=cross-border store
pageSizeNoNumber of items per page. **must be a multiple of 10, the maximum is 100**; the upper limit of a single page in the official interface is 10, internally it is 10 after multiple pulls per page and then merged
sortTypeNoSorting method: 0=ascending order (asc), 1=descending order (desc)
salesFlagNoMain delivery methods: 1=video, 2=live broadcast
categoryIdNoStore-level category ID. Maximum length 1000
categoryL2IdNoStore secondary category ID. Maximum length 1000
categoryL3IdNoThe third-level category ID of the store. Maximum length 1000
salesTrendFlagNoSales trend in the past 7 days: 0=stable, 1=increasing, 2=declining
maxFirstCrawlDtNoEstimated shelf time filter (maximum value), yyyyMMdd format
minFirstCrawlDtNoEstimated shelf time filter (minimum value), yyyyMMdd format (for example, 20240101 represents 2024-01-01)
sellerSortFieldNoSorting fields: 1=total sales (total_sale_cnt), 2=total sales (total_sale_gmv_amt), 3=average price of product SKU in the store (spu_avg_price)
maxTotalSaleGmv30dAmtNoGMV filtering in the past 30 days (maximum value)
minTotalSaleGmv30dAmtNoGMV screening in the past 30 days (minimum value)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds nothing beyond that — no note on pagination behavior, result caps, or that the data is a snapshot of TikTok seller/store listings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than efficiency. The single sentence contains no information beyond the tool name, so no sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 15-parameter listing tool with no output schema and only boilerplate safety annotations needs the description to explain result shape, scope (sellers vs. products), and pagination. None of that is present, so an agent cannot confidently select or invoke it.

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 all 15 parameters (region, pagination, category filters, GMV bounds, sort fields) are already documented in the schema. The description contributes no additional parameter meaning, which is the baseline expectation at full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely restates the name and title ('TikTok Intelligence ET: list Seller API') without a verb+resource explanation an agent can act on. It does not distinguish this tool from close siblings such as nexscope_data_et_list_seller_product, nexscope_data_et_seller_detail, or nexscope_data_et_list_product.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool, when not to, or which sibling to prefer for adjacent queries. The agent is left to infer everything from the name alone.

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

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources