AliExpress
AliExpress Page Read MCP
Read a bounded public AliExpress page. Send a UUID requestId with either keyword and optional pageNum (1–20), or a supported public AliExpress url. Do not combine url with keyword or pageNum. The response provides a taskId. Poll GET /aliexpress/accessTasks/{taskId} with the same Nexscope API key to retrieve the completed page result.
AliExpress Page Read AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Read A Keyword Search Page
Prompt: Read the public AliExpress search page for [keyword] on page [page number]. Summarize only text actually returned by the completed task.
2. Read A Supported Public Page
Prompt: Read the supported AliExpress page at [page URL]. Report the visible text or access outcome without assuming dynamic product data was extracted.
What You Need to Provide
Connect Nexscope MCP and check current pricing before submitting a task. Keep the returned task ID and query its result with the same account.
A task receipt is not a completed collection. Report only returned records and preserve empty, partial, failed, or uncertain states.
Supply a UUID requestId and either a keyword with optional page number 1–20, or a supported URL. Do not combine the two input branches. Use nexscope_aliexpress_access_task_result.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_aliexpress_page_readhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "aliexpress-page-read-1",
"method": "tools/call",
"params": {
"name": "nexscope_aliexpress_page_read",
"arguments": {
"keyword": "wireless earbuds",
"pageNum": 1,
"requestId": "11111111-1111-4111-8111-111111111111"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Asynchronous task workflow
- 1. Create once
Keep the returned taskId.
- 2. Query with backoff
Use nexscope_aliexpress_access_task_result to check the returned taskId with gradual backoff. Follow the actual task status and do not resubmit the paid request.
- 3. Use final result
Stop at success, failure, or timeout.
{
"jsonrpc": "2.0",
"id": "aliexpress-page-read-result-1",
"method": "tools/call",
"params": {
"name": "nexscope_aliexpress_access_task_result",
"arguments": {
"taskId": "TASK_ID_FROM_THE_SUBMISSION_RESULT"
}
}
}Arguments
| Name | Type | Required | Description |
|---|---|---|---|
keyword | string | optional | The normalized keyword must be at most 120 characters. Minimum length: 1 Maximum length: 240 |
pageNum | integer | optional | Page number. Default: 1 Minimum: 1 Maximum: 20 |
requestId | string | required | Client-generated UUID. Reuse it when retrying an uncertain submission. Format: uuid |
url | string | optional | Supported AliExpress product detail or category navigation URL. Format: uri Maximum length: 2048 |
One of option 1 — requires keyword
One of option 2 — requires url
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | optional | 0 means the tool call succeeded; nonzero is a Nexscope error. |
cost | integer | optional | Cost value used by this API operation. |
data | object | null | optional | Data value used by this API operation. |
data.error | string | null | optional | Error value used by this API operation. |
data.result | any | optional | Provider result when available; null while pending or when no verified result exists. |
data.status | string | required | The current task state; a successful tool call does not mean collection has finished. |
data.taskId | string | required | Use this identifier with the corresponding AliExpress MCP task result tool. |
data.usage | object | required | Usage value used by this API operation. |
data.usage.chargedCredits | integer | optional | Charged credits value used by this API operation. |
data.usage.nexscopeBillingState | string | optional | Nexscope billing state value used by this API operation. |
data.usage.observedBytes | integer | optional | Observed bytes value used by this API operation. |
data.usage.supplierChargeState | string | optional | Supplier charge state value used by this API operation. |
msg | string | null | optional | Msg value used by this API operation. |
time | string | optional | Time value used by this API operation. |
traceId | string | null | optional | Trace id value used by this API operation. |
ts | integer | optional | Ts value used by this API operation. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
How do I read an AliExpress page?
Suggested Steps
Choose either keyword navigation or a supported URL, generate a UUID requestId, and submit once. Query nexscope_aliexpress_access_task_result with the taskId; report only text or access status returned.
About this sample: This is a submission and result-query workflow, not a verified supplier response. A paid call may finish empty, partially, or with an error; check the actual task state and usage.
View the Published Sample Data (JSON)
Published REST data example. Use Parameters & Response for MCP arguments when calling this tool.
Data Example
Sample request and response
Request parameters
{
"requestId": "d55c91b1-7352-4e24-84cc-d7c248ce48e8",
"keyword": "phone case",
"pageNum": 1
}Response
{
"code": 0,
"data": {
"status": "SUCCEEDED",
"result": {
"page": {
"title": "",
"finalUrl": "https://www.aliexpress.com/w/wholesale.html?SearchText=phone+case&page=1",
"productLinks": [],
"outcome": "READ",
"stopReason": "DOCUMENT_READ",
"observedBytes": 0,
"text": "Help\nCustomer Service\nDisputes & Reports\nReport IPR infringement\nBuyer Protection\nApp\n?\nShip to\nLanguage\nCurrency\nSave\nCart\nWish List\nAccount\n\nWelcome to AliExpress!\n\nWelcome back\n\nSign Out\n\nJoin Sign in\n\n?\nMy Orders\nMessage Center\nWish List\nMy Favorite Stores\nMy Coupons",
"requestedUrl": "https://www.aliexpress.com/w/wholesale.html?SearchText=phone+case&page=1"
}
}
}
}View the MCP Request & Response Format
Examples
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
{
"jsonrpc": "2.0",
"id": "aliexpress-page-read-example",
"method": "tools/call",
"params": {
"name": "nexscope_aliexpress_page_read",
"arguments": {
"keyword": "wireless earbuds",
"pageNum": 1,
"requestId": "11111111-1111-4111-8111-111111111111"
}
}
}MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.