Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress product detail

nexscope_aliexpress_product_detail

Submit a supported AliExpress product URL for detail collection. The supplier may return an empty or failed task.

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_product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAliExpress /item/{id}.html URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds a genuinely useful behavioral fact: the supplier may return an empty or failed task, warning the agent that failure is a normal outcome. However, it omits the async flow (whether a task ID is returned and how to retrieve results) and any auth or rate-limit context, which is a real gap for a submission tool.

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 no waste, and the action is front-loaded before the failure caveat. The brevity borders on under-specification given the async nature of the tool, but nothing is redundant.

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?

With no output schema and a non-read-only submission tool that has task-result siblings, the description should explain what is returned (task ID vs. payload) and how to obtain results. Instead it only warns of possible empty/failed tasks, leaving the agent unsure of the correct follow-up flow.

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 required parameter with 100% schema coverage that already documents the "AliExpress /item/{id}.html URL" format. The description's only addition is the word "supported," which hints at acceptance constraints without specifying them, so it does not meaningfully extend 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?

The description names a specific verb ("Submit") and a specific resource ("AliExpress product URL") for detail collection, so an agent can identify it as the AliExpress detail-fetch tool among the many *_product_detail siblings. It does not state how it differs from those siblings (e.g., async task submission vs. direct return), which keeps it at 4 rather than 5.

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: supply an AliExpress product URL when you want product details. There is no explicit guidance on when to prefer this over nexscope_aliexpress_product_search or the non-AliExpress detail siblings, no prerequisites, and no note about following up with a task-result tool, so it is minimal-viable.

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