Skip to main content
Glama

Tiktok New Product Rank

nexscope_tiktok_new_product_rank
Read-only

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the market breadth (16 regions) and the data source, but says nothing about result ordering, freshness/latency of ranking data, or pagination limits.

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?

Purpose is front-loaded well, but the trigger list is padded with duplicates ('TikTok new product rankings' appears twice, 'TikTok bestsellers' twice, plus redundant near-synonyms), consuming most of the text without adding selection signal.

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

Completeness4/5

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

A simple read-only ranking query with full schema coverage and annotations, so an agent has enough to invoke it correctly. Minor gaps remain around what the ranking is ordered by and whether the data is a snapshot for the given date.

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 four parameters are documented in the schema. The description only reinforces the '16 regional markets' aspect of the region parameter without adding syntax, defaults, or format detail beyond what the schema already provides — baseline 3.

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?

First sentence states a specific verb and resource ('Discover trending new products') plus scope ('across 16 TikTok Shop regional markets via Nexscope new product ranking data'). It does not, however, distinguish itself from closely related siblings such as nexscope_tiktok_top_selling_products or nexscope_chuhaijiang_tiktok_product_rankings_new_arrivals.

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?

The trigger list gives explicit user phrasings that should invoke the tool, and it explicitly extends coverage to cases where 'Nexscope' or 'new product ranking' are not mentioned. It stops short of saying when NOT to use it or which sibling to prefer for bestsellers vs. new arrivals vs. top-selling.

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.