Skip to main content
Glama

Nexscope Ecommerce Data MCP

TikTok Intelligence FM: product Search API

nexscope_data_fm_product_search
Read-only

TikTok Intelligence FM: product Search API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexscope_data_fm_product_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
regionNoMarket area code. Optional values: `US` (United States), `GB` (UK), `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).
isSshopNoFilter only TikTok fully hosted (S-shop) items.
keywordNoSearch keywords (fuzzy matching of product titles).
categoryNoFor English category names, the system automatically matches the TikTok category ID; non-English names need to be translated into English first.
pageSizeNoNumber of items per page, maximum `10`.
shopTypeNoStore type: `1`=local store, `2`=cross-border store.
orderFieldNoSorting fields: `day7_units_sold` (7-day sales), `day7_gmv` (7-day GMV), `commission_rate` (commission rate), `total_units_sold` (total sales), `total_gmv` (total GMV), `creator_count` (number of customers). Default is descending order.
isNewListedNoOnly filter new listings.
isTopSellingNoFilter only the best-selling items.
isFreeShippingNoFilter only free shipping products.
unitsSoldRangeNoSales range filtering, format: `{"min": 100, "max": 5000}`.
isLocalWarehouseNoOnly filter products shipped from local warehouses.
creatorCountRangeNoFilter the number of people carrying goods, format: `{"min": 10, "max": 500}`.
commissionRateRangeNoCommission rate range filtering, format: `{"min": 0.05, "max": 0.20}` (decimal, `0.10`=10%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / pageSize / maximum
      Added value: +10
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
  2. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered structurally. The description contributes nothing beyond that: no mention of pagination limits, result caps, ordering defaults, data freshness, or coverage of markets. For a 15-parameter query tool, that is a real gap in behavioral context.

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

Conciseness3/5

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

It is a single short sentence with no filler, so nothing is wasteful. However, it is under-specified rather than concise — brevity here reflects missing content, not disciplined editing, and it is not front-loaded with any actionable information.

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

Completeness2/5

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

Given 15 optional parameters, nested range filters, an enum, and no output schema, the description should explain return shape, paging behavior, and default sort semantics. None of that is present, leaving the agent to infer everything from the schema and annotations alone.

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% — every one of the 15 parameters, including the nested range objects and the region enum, is documented in the schema itself. Per the baseline rule this yields a 3; the description adds no extra meaning (e.g., how range objects combine with filters, or how orderField interacts with paging).

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 is essentially the title restated: "TikTok Intelligence FM: product Search API." It conveys a resource (TikTok FM products) and implies search, but adds no scope, no distinguishing detail versus the many sibling product_search tools (nexscope_tiktok_product_search, nexscope_data_ss_product_search, etc.), and reads as tautology rather than explanation.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative guidance at all. The agent is not told how this differs from sibling TikTok or product search tools, nor what prerequisites or account context apply. The only hint is the tool name itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources