1688 Procurement

1688 Logistics Trace MCP

Review the tracking events and delivery progress for a 1688 order. Requires an active 1688 authorization and your Nexscope API key.

Cost10 credits / callOnline Test

1688 Logistics Trace 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 Order Tracking Events

Prompt: For my 1688 order [ALI_ORDER_ID], retrieve the returned tracking events in their source order. Show the recorded locations and times; do not infer an unreported delivery date.

2. Track A Selected Shipment

Prompt: For 1688 order [ALI_ORDER_ID] with multiple shipments, use the selected logisticsId [LOGISTICS_ID] to retrieve its trace. Keep events for other shipments separate.

What You Need to Provide

Replace bracketed values with your own identifiers and inputs. Use only your own ACTIVE, unexpired 1688 store authorization.

Read the returned business status and message. An HTTP or envelope success does not prove that an order or write operation succeeded.

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/json

Authentication

Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Using an API key? Get your key from API Access and include it in the Authorization header shown above.

Call this MCP tool

MCP tool name

nexscope_data_alibaba1688_logistics_trace

MCP endpoint

https://api.nexscope.ai/mcp

JSON-RPC method

tools/call

Initialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.

{
  "jsonrpc": "2.0",
  "id": "1688-logistics-trace-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_alibaba1688_logistics_trace",
    "arguments": {
      "aliOrderId": "3309156590237728779"
    }
  }
}

MCP 2025-11-25 · Streamable HTTP

Progress 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
`aliOrderId`	`string`	required	Exact positive integer identifier. Send as a JSON string. Example: 3309156590237728779
`logisticsId`	`string`	optional	Select a logistics order when multiple shipments exist.

Response fields

Treat structuredContent as the programmatic API response payload.

Name	Type	Required	Description
`code`	`integer`	optional	Nexscope transport/business envelope code; 0 means the request was processed. Inspect data for operation outcomes.
`cost`	`string`	optional	Processing time in milliseconds, not credits.
`data`	`object`	optional	Data value used by this API operation.
`data.aliOrderId`	`string`	optional	Exact positive integer identifier. Send as a JSON string. Pattern: ^[1-9][0-9]*$
`data.logisticsId`	`string`	optional	Logistics id value used by this API operation.
`data.traceList`	`array`	optional	Trace list value used by this API operation.
`data.traceList[]`	`object`	required	Item in data traceList.
`data.traceList[].location`	`string`	optional	Location value used by this API operation.
`data.traceList[].traceDescription`	`string`	optional	Trace description value used by this API operation.
`data.traceList[].traceStatus`	`string`	optional	Trace status value used by this API operation.
`data.traceList[].traceTime`	`string`	optional	Asia/Shanghai time.
`msg`	`string \| null`	optional	Safe response message.
`time`	`string`	optional	Server response time.
`traceId`	`string \| null`	optional	Request trace identifier.
`ts`	`string`	optional	Server timestamp.

Format Illustration

Illustrative example with fictional data, not a live tool call.

Illustrative Question

For my 1688 order [ALI_ORDER_ID], retrieve the returned tracking events in their source order. Show the recorded locations and times; do not infer an unreported delivery date.

Illustrative Response Explanation

The traceList contains tracking events for the requested order or selected logisticsId. Keep source times and locations, and do not invent an arrival estimate.

About this sample: This is an illustrative documentation example, not a live response from your account. Check the actual returned fields and status.

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