1688 Sourcing
1688 Search By Image MCP
Find visually similar 1688 supplier products from an image URL. Call the 1688 Search By Image API via REST or MCP with your Nexscope API key.
1688 Search By Image 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. Find Similar 1688 Products
Prompt: Find Similar 1688 Products using [public image link], refined by [search phrase in Simplified Chinese]. Show the available results and clearly identify missing information.
2. Find Similar 1688 Products By Public Image Link
Prompt: Find Similar 1688 Products using [public image link]. Keep the returned results tied to that input and do not infer matches that were not returned.
3. Find Similar 1688 Products By Uploaded Image
Prompt: Find Similar 1688 Products using [uploaded image]. Keep the returned results tied to that input and do not infer matches that were not returned.
4. Reuse An Image Search Reference
Prompt: Find Similar 1688 Products using [previously returned image reference]. Keep the returned results tied to that input and do not infer matches that were not returned.
5. Continue The Results Within A Page Limit
Prompt: Find Similar 1688 Products using [previously returned image reference], refined by [search phrase in Simplified Chinese]. Start at [my selected page] and return [my requested page size] within the documented limits. Ask before requesting another page and do not describe one page as the complete dataset.
6. Prioritize The Results For Review
Prompt: Find Similar 1688 Products using [public image link], refined by [search phrase in Simplified Chinese]. Prioritize [my chosen ranking metric] in [my chosen order]. Keep the ranking limited to the selected filters and reporting period. Rank by price, monthly units sold, or repurchase rate in ascending or descending order.
7. Find Similar Products Within A Price Range
Prompt: Find 1688 products similar to [public image link], refine the image matches with [search phrase in Simplified Chinese], and keep prices between [minimum price in CNY] and [maximum price in CNY]. Summarize the matching offers.
8. Narrow The Image Matches
Prompt: Find Similar 1688 Products using [public image link], refined by [search phrase in Simplified Chinese]. Apply [my sourcing requirements] to the visually similar products. Report only what the selected records support.
What You Need to Provide
Replace bracketed inputs with your own values. Use only the documented marketplace, period and input formats.
Returned estimates and rankings describe the selected data and period; missing values are not zero and a page of results is not the full market.
Provide an image you can access and use. Visual similarity alone does not prove product identity, brand ownership or supplier authorization.
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_1688_search_by_imagehttps://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-search-by-image-1",
"method": "tools/call",
"params": {
"name": "nexscope_1688_search_by_image",
"arguments": {
"imageUrl": "https://m.media-amazon.com/images/I/61v6nYvQ7+L._AC_SL1500_.jpg",
"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 |
|---|---|---|---|
imageUrl | string | optional | Public HTTP/80 or HTTPS/443 URL, maximum 1,000 characters, without redirects. A sole direct source is checked for PNG/JPEG headers, at most 14.3 MiB, each dimension at most 20,000 and at most 40,000,000 pixels. This is not full pixel-integrity validation. Provide exactly one of imageUrl, imageBase64, or imageId. Example: https://m.media-amazon.com/images/I/61v6nYvQ7+L._AC_SL1500_.jpg |
imageBase64 | string | optional | Raw standard Base64 for PNG/JPEG; optional padding and outer whitespace allowed, embedded whitespace and data URI prefixes rejected for a sole direct source. Byte/header limits match imageUrl; at most 19,992,848 Base64 characters after outer whitespace trimming. Provide this as the only image source. |
imageId | string | optional | 1688 image ID. Image-search results also return this value; include it when page is greater than 1 to improve response time |
page | integer | optional | Page number starting from 1 Example: 1 |
pageSize | integer | optional | Number of products per page; default 20, maximum 50 Example: 20 |
priceStart | string | optional | Minimum price in CNY, for example 10 |
priceEnd | string | optional | Maximum price in CNY, for example 100 |
filter | string | optional | Comma-separated filter conditions. Use the supported filter values documented for this endpoint |
sort | string | optional | Sort condition as JSON in the form {field: direction}. Fields: price, rePurchaseRate, or monthSold. Directions: asc or desc |
keyword | string | optional | Keyword used to search within the results Example: phone case |
productCollectionId | string | optional | Single product-collection ID. Use a supported collection ID documented for this endpoint Example: example-id |
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.columns | array | optional | Render column definition |
data.columns[] | any | required | Render column definition |
data.imageId | string | optional | The image ID after uploading; returning it during paging query can speed up the process |
data.products | array | optional | Products value used by this API operation. |
data.products[] | object | required | Item in data products. |
data.products[].asin | string | optional | Item number, same as `offerId` |
data.products[].asinUrl | string | optional | Product link |
data.products[].compositeServiceScore | string | optional | Comprehensive service experience points |
data.products[].consignPrice | number | optional | Price for one piece (yuan) |
data.products[].currency | string | optional | Currency, fixed to `Â¥` |
data.products[].dataType | string | optional | Data type, fixed to `monthlyData` |
data.products[].deliveryTime | string | optional | Shipping time (24/48 hours) |
data.products[].estimatedSalesAmount | number | optional | Estimated sales |
data.products[].hasPromotion | string | optional | Is there a marketing campaign (yes/no) |
data.products[].imageUrl | string | optional | Product pictures |
data.products[].isJxhy | string | optional | Whether to select supply sources (yes/no) |
data.products[].isOnePsale | string | optional | Whether to ship on behalf of one piece (yes/no) |
data.products[].isPatentProduct | string | optional | Is it a patented product (yes/no) |
data.products[].isSelect | string | optional | Cross-Border Select Pallet Identification |
data.products[].offerId | string | optional | Product ID |
data.products[].offerIdentities | string | optional | Product label (carefully selected) |
data.products[].price | number | optional | Wholesale price (yuan) |
data.products[].promotionType | string | optional | marketing type |
data.products[].quantityBegin | integer | optional | Minimum batch size |
data.products[].repurchaseRate | string | optional | Repurchase rate |
data.products[].salesQuantity | integer | optional | Number of pieces sold per month |
data.products[].sellerIdentities | string | optional | Merchant identity (super factory/powerful merchant/integrity member) |
data.products[].sendGoodsAddressText | string | optional | Place of shipment |
data.products[].sourceType | string | optional | Source type, fixed to `1688` |
data.products[].title | string | optional | Product title |
data.products[].tradeScore | string | optional | Product Transaction Rating |
data.sourceType | string | optional | Source type, fixed to `1688` |
data.total | integer | optional | Quantity of products on this page |
data.totalPage | integer | optional | Total pages |
data.type | string | optional | Rendering style, fixed to `productWorkbenches` |
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
Find visually similar 1688 supplier products.
Illustrative Response Explanation
The illustrative result shows title: Example record; asin: example-asin; offer id: example-offerId. These figures describe only the shown record. Missing measures cannot be calculated from this example.
About this sample: Illustrative example with fictional records, not a live tool call. Identifiers, prices and counts are demonstration values.
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
Illustrative example with fictional data, not a live tool call.
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": "1688-search-by-image-example",
"method": "tools/call",
"params": {
"name": "nexscope_1688_search_by_image",
"arguments": {
"imageUrl": "https://m.media-amazon.com/images/I/61v6nYvQ7+L._AC_SL1500_.jpg",
"page": 1,
"pageSize": 20
}
}
}MCP Response Format
{
"jsonrpc": "2.0",
"id": "1688-search-by-image-example",
"result": {
"content": [
{
"type": "text",
"text": "{\"code\":0,\"msg\":null,\"data\":{\"products\":[{\"title\":\"Example record\",\"asin\":\"example-asin\",\"offerId\":\"example-offerId\",\"price\":19.99}]}}"
}
],
"structuredContent": {
"code": 0,
"msg": null,
"data": {
"products": [
{
"title": "Example record",
"asin": "example-asin",
"offerId": "example-offerId",
"price": 19.99
}
]
}
},
"isError": false
}
}