Nexscope Ecommerce Data MCP

Tiktok Video Search

nexscope_tiktok_video_search

Search and analyze TikTok video data, filter videos by region, creator, product, category, views, duration, publish time, selling/ad/AI video flags, and return views, likes, comments, shares, favorites, video sales and GMV metrics across 16 TikTok Shop sites. Trigger when users mention TikTok video search, TikTok video list, TikTok promotional videos, TikTok video data, TikTok video views, TikTok video sales, TikTok video analytics, Nexscope video, TikTok video search, TikTok video list, TikTok video analytics, TikTok promotional videos, TikTok video views, TikTok video engagement. Even if the user does not explicitly mention "Nexscope" or "TikTok", trigger this skill whenever their need involves searching or analyzing TikTok video performance metrics by criteria.

Input Schema

Name	Required	Description
`isAd`	No	Whether an ad video: 0=non-ad video, 1=ad video
`region`	Yes	Region code. 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)
`userId`	No	Creator ID filter. Max length 1000
`pageNum`	No	Page number, starting from 1
`pageSize`	No	Items per page, default 50. Must be a multiple of 10, max 100; the third-party API limit is 10 per page, internally the gateway fetches 10 per page in multiple rounds and merges
`sortType`	No	Sort direction: 0=ascending, 1=descending
`productId`	No	Associated product ID. Max length 1000
`salesFlag`	No	Whether a promotional video: 0=non-promotional video, 1=promotional video
`createdByAi`	No	AI video filter; accepts only the strings "true" or "false", not a JSON boolean
`maxDuration`	No	Video duration range filter (seconds) - maximum
`minDuration`	No	Video duration range filter (seconds) - minimum
`maxCreateTime`	No	Publish time range filter (seconds-level timestamp) - maximum
`minCreateTime`	No	Publish time range filter (seconds-level timestamp) - minimum
`videoSortField`	No	Sort field, default 3: 1=total_digg_cnt (likes), 2=create_time (publish time), 3=total_views_cnt (views)
`maxTotalViewsCnt`	No	Video view count filter (maximum)
`minTotalViewsCnt`	No	Video view count filter (minimum)
`productCategoryId`	No	Associated product category ID. Max length 1000

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

While the annotations are minimal, the description provides significant behavioral context by explicitly listing the metrics it returns (views, likes, comments, shares, GMV) and the types of flags it filters by (selling/ad/AI video flags). This goes beyond the static schema details.

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 definition is extremely verbose. The second half, which is a massive keyword dump, adds virtually no functional value to the AI agent and significantly hinders readability and parsing.

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

Completeness5/5

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

Given the high complexity (17 parameters) and the wide array of data points involved (metrics, flags, filters, regions), the description is necessary and comprehensive enough to guide the agent's intent mapping.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema coverage is 100%, the description focuses on adding high-level semantics, such as defining the comprehensive scope (16 TikTok Shop sites) and detailing the types of metrics (GMV, sales) the data encompasses, which helps the agent frame user intent.

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

Purpose5/5

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

The description clearly states the tool's function: 'Search and analyze TikTok video data.' It specifies the resource (video data) and the massive scope (metrics across 16 TikTok Shop sites), clearly defining its niche among siblings.

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

Usage Guidelines5/5

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

The description provides an extensive list of trigger phrases (e.g., 'TikTok promotional videos,' 'TikTok video sales,' 'Nexscope video'). This acts as an exhaustive usage guide, explicitly telling the agent exactly when to call this tool versus other potential search tools.

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

All Nexscope Ecommerce Data MCP tools Inspect

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

Need Help?