Skip to main content
Glama

Nexscope Ecommerce Data MCP

Tiktok New Product Rank

nexscope_tiktok_new_product_rank

Discover trending new products across 16 TikTok Shop regional markets via Nexscope new product ranking data. Trigger when users mention TikTok new product rankings, TikTok hot-selling products, TikTok Shop bestsellers, short-video e-commerce product selection, TikTok new product discovery, cross-border TikTok product selection, TikTok new product rankings, TikTok bestsellers, short-video product selection, TikTok viral products, new product ranking, TikTok product trends. Even if the user does not explicitly mention "Nexscope" or "new product ranking", trigger this skill whenever their need involves discovering hot-selling new products or emerging product trends on TikTok Shop.

Input Schema

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
regionNoRegion, default US. Options: US (United States), ID (Indonesia), TH (Thailand), PH (Philippines), MY (Malaysia), VN (Vietnam), GB (United Kingdom), MX (Mexico), SG (Singapore), SA (Saudi Arabia), BR (Brazil), ES (Spain), JP (Japan), DE (Germany), IT (Italy), FR (France)
pageNumNoPage number, default 1
pageSizeNoItems per page, default 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The only behavioral detail is the 16-market coverage. With a thin annotation set (readOnlyHint=false, openWorldHint=true) the description should carry the load, yet it says nothing about data freshness, the ranking window behind 'new', pagination ceilings, or how results are ordered. Most of the text is a keyword list rather than behavioral disclosure.

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?

The synonym list is padded and repetitive, with 'TikTok new product rankings' and 'TikTok bestsellers' each appearing twice, and terms like 'short-video product selection' offered with no discriminating value. Length comes from keyword surfacing rather than 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?

There is no output schema and no explanation of what the ranking rows contain (sales, GMV growth, rank position, category). For a discovery/ranking tool an agent still cannot tell what it will get back or how the date parameter affects the result set.

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%, with the date format and the full 16-region enum already documented in the schema, so baseline 3 applies. The description's mention of '16 TikTok Shop regional markets' only restates what the region enum provides.

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

Purpose4/5

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

States a specific verb and resource: discover trending new products via new product ranking data, scoped to 16 TikTok Shop regional markets. It does not differentiate itself from close siblings such as nexscope_tiktok_top_selling_products, nexscope_tiktok_product_discovery, or the various *_products_rankings_new_arrivals tools.

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

Usage Guidelines4/5

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

Gives explicit trigger conditions, including that the user need not say 'Nexscope', which is useful routing context. It stops short of exclusions or naming alternatives, so an agent cannot tell from the text alone when to prefer the top-selling or new-arrivals ranking siblings instead.

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