Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Category Trend

nexscope_data_et_category_trend
Read-only

Read one page of TikTok category daily trends.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "nexscope_data_et_category_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesTwo-letter uppercase region.
endDateYesEnd date, yyyy-MM-dd.
pageNumNoOne page per call.
pageSizeNoRecords per page, at most 10.
startDateYesStart date, yyyy-MM-dd.
categoryIdNoOptional category ID.
categoryL2IdNoOptional category ID.
categoryL3IdNoOptional category ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so safety behavior is covered. The description adds only "one page," which is already conveyed by the pageNum schema field, and says nothing about data freshness, region coverage, historical limits, auth requirements, or what daily trend records contain.

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

Conciseness4/5

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

The definition is a single front-loaded sentence with no filler or repetition. It is efficient, though its brevity contributes to the broader incompleteness of the definition rather than being a flaw in conciseness itself.

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?

This is an eight-parameter tool with date ranges, three optional category levels, and pagination, and there is no output schema. The description does not explain what a trend record contains, how category IDs should be selected, or any limits on historical range, so it is substantially incomplete for the tool's complexity.

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 eight parameters are documented in the schema itself. The description adds no additional meaning about date ranges, category-level filtering, or pagination beyond what the schema already provides, which meets the baseline of 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?

The description states a specific verb ("Read") and resource ("TikTok category daily trends"), with the scope limited to "one page." It is clear enough for an agent to understand the general operation, but it does not distinguish this from sibling tools such as category detail or other trend endpoints.

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?

The description gives no guidance on when to use this tool versus alternatives like nexscope_data_et_category_detail or the category L1/L2/L3 tools. There are no exclusions, prerequisites, or contextual cues beyond the bare purpose statement.

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