Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Category Overview

nexscope_data_et_category_detail
Read-only

Read a top-level TikTok category overview; data is updated T+1.

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": {
      "categoryId": "<categoryId>",
      "region": "<region>"
    },
    "name": "nexscope_data_et_category_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYesTwo-letter uppercase region.
categoryIdYesTop-level category ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's main contribution is the 'T+1' freshness signal, which is genuinely useful for judging data staleness. However, it says nothing about the response shape or any rate/quota behavior, which matters for an open-world data API.

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

Conciseness5/5

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

A single sentence, front-loaded with the action and resource, with the freshness note compressed into a clause. Nothing is redundant or padded.

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?

For a simple two-parameter read tool with full schema coverage and complete safety annotations, the definition covers purpose, scope and data latency. The notable remaining gap is what the 'overview' actually contains (metrics/fields), which matters given there is no output schema; a brief mention of returned dimensions would make it complete.

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?

Schema description coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds real meaning beyond the schema: 'top-level' implies categoryId must be a top-level category ID, a constraint the '[0-9]{1,100}' pattern does not convey.

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 uses a clear verb+resource pair ('Read a top-level TikTok category overview') and the qualifier 'top-level' separates it in spirit from the sibling l1/l2/l3 category tools. It stops short of naming those siblings, so an agent must infer the boundary rather than being told it.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'top-level' — an agent can guess this is for high-level category data rather than subcategory breakdowns. There is no explicit when-to-use/when-not-to-use statement, no pointer to nexscope_data_et_category_l1/l2/l3, and no prerequisite guidance such as how to obtain a valid categoryId.

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