Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress category variants

nexscope_aliexpress_category_variants

Collect observed variants through a supported AliExpress category URL. The limit bounds product groups, not variant rows.

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": {
      "url": "<url>"
    },
    "name": "nexscope_aliexpress_category_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSupported AliExpress category navigation URL.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so safety and world-access are covered structured-side. The description adds one genuinely useful behavioral fact — that the limit bounds product groups rather than variant rows, which tells the agent how result volume scales — but it does not disclose collection latency, whether a task handle is returned, or error/unsupported-URL behavior. 'Collect' also reads as a retrieval verb against a readOnlyHint=false annotation, which is ambiguous rather than contradictory.

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?

Two short sentences, action first, clarifying caveat second. No filler and nothing redundant with the schema.

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?

Adequate for a two-parameter tool with no output schema, but key gaps remain: what 'supported' URLs look like, whether the call is synchronous or returns a task id (relevant given the task_result siblings), and what a returned variant row contains. An agent could call it, but not confidently predict the result shape or failure modes.

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 coverage is only 50% — 'url' is described, 'limit' has no description beyond default/min/max. The sentence 'The limit bounds product groups, not variant rows' supplies exactly the missing semantics and is essential for predicting output size, going beyond the schema.

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?

States a concrete verb and resource: 'Collect observed variants' scoped to an AliExpress category URL. This is distinguishable from the sibling nexscope_aliexpress_category_products (products vs. variants), though the description never explicitly contrasts with it and leaves 'variants' somewhat underspecified (what row shape, what fields).

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 prerequisites, and no pointer to alternatives such as category_products or the task_result tools that likely accompany an open-world collection operation. The only usage-flavored statement is the URL must be a 'supported' category navigation URL, which raises a constraint without saying how to tell what is supported.

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