Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Level 1 Categories

nexscope_data_et_category_l1
Read-only

List TikTok top-level product categories in the requested language.

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": {
      "language": "<language>"
    },
    "name": "nexscope_data_et_category_l1"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesResponse language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the response is localized to the requested language; it says nothing about whether the result is a flat list, whether it includes category IDs needed for follow-up calls, or how large the payload is.

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?

One sentence, front-loaded with the verb and resource, and it carries the two pieces of information that matter (scope and localization). There is no filler or redundant restatement of the title.

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

Completeness3/5

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

For a trivial single-parameter lookup with full schema coverage and read-only annotations, the definition is close to sufficient. The notable gap is that it does not tell the agent what a category entry contains or whether the returned identifiers are what the category_detail/l2 tools expect, which matters for chaining.

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?

There is a single parameter with 100% schema description coverage and an explicit enum of six locales, so the schema does the heavy lifting. The phrase "in the requested language" reinforces that language controls the response locale rather than filtering results, but adds no detail beyond the schema's "Response language."

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?

"List TikTok top-level product categories" gives a specific verb plus resource, and "top-level" distinguishes it from the L2/L3 category siblings without needing to name them. It falls short of a 5 only because it never explicitly names the deeper-level alternatives an agent must choose between.

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?

The word "top-level" implies this is the entry point of the category hierarchy, which is a weak form of when-to-use guidance. There is no explicit statement about when to prefer this over nexscope_data_et_category_l2 or nexscope_data_et_category_detail, and no prerequisites are mentioned.

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