Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

TikTok Intelligence ET: list Video API

nexscope_data_et_list_video
Read-only

TikTok Intelligence ET: list Video API.

Input Schema

NameRequiredDescriptionDefault
isAdNoWhether to stream video: 0 = no streaming video, 1 = streaming video
regionYesArea code. 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)
userIdNoExpert ID filtering. Maximum length 1000
pageNumNoPagination page number, starting from 1
pageSizeNoNumber of items per page. **Must be a multiple of 10, the maximum is 100**; the upper limit for a single page of the third-party interface is 10, internally press 10 for each page to be pulled multiple times and then merged
sortTypeNoSorting method: 0=ascending order (asc), 1=descending order (desc)
productIdNoProduct ID associated with the video. Maximum length 1000
salesFlagNoWhether to bring goods video: 0 = no goods carrying video, 1 = goods carrying video
createdByAiNoWhether AI video, only accepts the string `"true"` (AI video) or `"false"` (non-AI video), non-Boolean
maxDurationNoVideo duration range filtering (seconds) - maximum value
minDurationNoVideo duration range filtering (seconds) - minimum value
maxCreateTimeNoRelease time range filtering (second-level timestamp) - maximum value
minCreateTimeNoRelease time range filtering (second-level timestamp)-minimum value
videoSortFieldNoSorting fields: 1=total_digg_cnt (number of likes), 2=create_time (release time), 3=total_views_cnt (number of views)
maxTotalViewsCntNoVideo playback filter (maximum value)
minTotalViewsCntNoVideo playback filter (minimum value)
productCategoryIdNoAssociated product category ID. Maximum length 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: no mention of rate limits, data freshness, third-party paging aggregation (which the schema hints at), or auth requirements.

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?

A single short sentence that is not front-loaded with useful content — it is concise only because it says almost nothing. Brevity here signals under-specification rather than efficiency.

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?

For a 17-parameter list/search tool with no output schema, the description should at minimum explain what a returned video record contains and how filters combine. None of that is present, leaving the agent to infer everything from parameter names.

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% and all 17 parameters carry their own explanations, so the description is not required to compensate. Baseline 3 applies; the description itself contributes no parameter meaning.

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 restates the title nearly verbatim ('TikTok Intelligence ET: list Video API') without saying what a 'Video' entity is, what is returned, or how it differs from the many sibling video tools (nexscope_tiktok_video_search, nexscope_data_et_list_video_rank, nexscope_data_et_list_product_video). It is essentially a tautology of the name.

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?

No when-to-use guidance, no exclusions, no mention of alternatives. An agent cannot tell from the text whether to use this versus nexscope_tiktok_video_search or nexscope_data_et_list_video_rank; only the word 'list' hints at enumeration.

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