Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress page read

nexscope_aliexpress_page_read

Read a bounded public AliExpress page by keyword or supported URL. This does not guarantee dynamic product extraction.

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": {
      "requestId": "<requestId>"
    },
    "name": "nexscope_aliexpress_page_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSupported AliExpress product detail or category navigation URL.
keywordNoThe normalized keyword must be at most 120 characters.
pageNumNo
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

The description adds two genuinely useful caveats beyond the annotations: the page read is 'bounded' and public, and dynamic product extraction is not guaranteed. However, the required requestId plus readOnlyHint=false strongly suggest an async job creation step that the description never discloses, and it says nothing about rate limits, permissions, or what a caller gets back.

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?

Two short sentences, with the core capability front-loaded and the caveat second. No padding, though the caveat would be sharper if it said exactly which dynamic fields can be missing.

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?

There is no output schema, the tool appears asynchronous (required requestId, task-result siblings), and the description never explains the request/result lifecycle or what the read returns. For a four-parameter fetch with an opaque correlation id, this leaves key agent decisions unaddressed.

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 coverage is 50%: url and keyword are documented in the schema, while pageNum and requestId are not. The description adds only the vague notion of a 'bounded' page (pageNum caps at 20) and does not say whether keyword and url are mutually exclusive or how requestId correlates the call to a later task result.

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 and resource: 'Read a bounded public AliExpress page' with two input modes ('by keyword or supported URL'). It does not name or contrast any sibling such as nexscope_aliexpress_product_detail or nexscope_aliexpress_product_search, which is the most obvious confusion risk for an agent choosing a carrier.

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 input modes (keyword or supported URL) imply when the tool applies, and 'supported' hints that not all URLs work. But there is no explicit when-not-to-use, no alternative named, and 'supported' is never defined, leaving the agent to guess which URLs qualify.

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