1688 Procurement
1688 Order List MCP
List one page of the current buyer's 1688 orders, with status, date and seller filters. Current and historical orders are paged separately.
1688 Order List 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. Review Current Buyer Orders
Prompt: Show the current buyer's recent 1688 orders. Return the order IDs and available statuses from the first page, and tell me whether another page exists.
2. Find Historical Buyer Orders
Prompt: Find historical 1688 orders for my connected buyer account within [CREATION_DATE_RANGE]. Show the returned orders and keep historical and current pages separate.
3. Check Orders By Status
Prompt: List my 1688 orders matching [ORDER_STATUS] and [REFUND_STATUS]. Keep the two filters distinct and report only statuses actually returned.
4. Locate A Seller Or Product Order
Prompt: Find my 1688 orders for seller [SELLER_LOGIN_OR_MEMBER_ID] or product [PRODUCT_NAME]. Use the seller identifier I provide, and do not switch buyer accounts.
5. Review Recently Modified Orders
Prompt: Show my 1688 orders modified within [MODIFICATION_DATE_RANGE]. Review at most [PAGE_LIMIT] pages and stop earlier if the response says there are no more pages.
What You Need to Provide
Use the current buyer's existing 1688 authorization. Current and historical tables have separate pagination; stop at the requested page limit or when hasNext is false.
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_data_alibaba1688_order_listhttps://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": "1688-order-list-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_alibaba1688_order_list",
"arguments": {
"isHis": false,
"page": 1,
"pageSize": 20
}
}
}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.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
page | integer | optional | Page number, starting at 1. Example: 1 |
pageSize | integer | optional | Orders per page, 1 to 20. Example: 20 |
orderStatus | string | optional | Original 1688 order status filter. |
refundStatus | string | optional | Refund status filter. |
createStartTime | string | optional | Creation start time with a timezone. |
createEndTime | string | optional | Creation end time with a timezone. |
modifyStartTime | string | optional | Modification start time with a timezone. |
modifyEndTime | string | optional | Modification end time with a timezone. |
sellerLoginId | string | optional | Seller login filter; does not switch the buyer. |
sellerMemberId | string | optional | Seller member filter; does not switch the buyer. |
productName | string | optional | Product name filter. |
isHis | boolean | optional | False selects current orders; true selects historical orders. Example: false |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
hasNext | boolean | required | Has next value used by this API operation. |
isHis | boolean | required | Is his value used by this API operation. |
orders | array | required | Orders value used by this API operation. |
orders[] | object | required | Item in orders. |
page | integer | required | Page value used by this API operation. |
pageSize | integer | required | Page size value used by this API operation. |
totalRecord | integer | required | Total record value used by this API operation. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
How can I review my 1688 orders in this API?
Suggested Steps
Workflow example: list one page for the currently authorized buyer. Choose current or historical orders, then add status, seller, product, creation-time, or modification-time filters as needed. Follow `hasNext` only within a user-chosen page limit; the two order tables are paged separately. No verified order result is published for this page.
About this sample: Workflow guidance based on the documented request and response fields; no buyer order data or live response is shown.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
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
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
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.