Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress product search

nexscope_aliexpress_product_search

Search public AliExpress product listings by keyword. Returns an asynchronous task receipt; query the task result to inspect products.

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": {
      "keyword": "<keyword>"
    },
    "name": "nexscope_aliexpress_product_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYesThe normalized keyword must be at most 120 characters.
pageNumNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the crucial non-obvious trait that this is asynchronous and returns a task receipt rather than products. It omits rate limits, auth requirements, and task expiry, so it adds solid but not complete behavioral context.

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 sentences, zero padding, with the async return behavior front-loaded before the follow-up action. Every clause conveys information the agent needs to act.

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?

The async workflow disclosure is the essential piece and it is present, which is good for a no-output-schema tool. However, paging boundaries (limit max 100, pageNum max 20) and the unresolved keyword-length conflict are left entirely to the schema, leaving the agent without guidance on result-set traversal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description is expected to compensate, and it does not — limit and pageNum receive no explanation of paging semantics or caps. The only documented parameter carries a confusing constraint ("at most 120 characters") that conflicts with the schema's maxLength of 240, and the description does nothing to clarify it.

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 names a specific verb and resource ("Search public AliExpress product listings") and a retrieval mode ("by keyword"), which separates it from category-browsing or detail siblings. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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?

It gives a useful follow-up step ("query the task result to inspect products"), which is real usage guidance for an async tool. It never names the actual result tool despite having two candidates in the catalog, and offers no when-not-to-use condition or alternative for category-based browsing.

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