Skip to main content
Glama
Sign In

Nexscope

by io.github.nexscope
OverviewDiscussionsAdmin

1688 Sourcing: image Search API

nexscope_data_alibaba1688_image_search
Read-only

1688 Sourcing: image Search API. Supply a JPEG/PNG image URL, pure Base64, or a returned imageId. Direct API calls do not perform the Skill image conversion step.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting from 1
sortNoJSON-encoded string: price, rePurchaseRate, or monthSold with asc or desc.{"monthSold":"desc"}
filterNoComma-separated filters: 1688Selection, certifiedFactory, totalEpScoreLv1, totalEpScoreLv2, totalEpScoreLv3, totalEpScoreLv4, qrr0, qrr1, qrr5, qrr10, shipInToday, shipIn24Hours, shipIn48Hours, noReason7DReturn, isOnePsale, isOnePsaleFreePost, new7, new30, isQqyx, JPFL, USFL, KRFL, VNFL, SAFL, RUFL, KZFL, HKFL, MOFL, TWFL.
imageIdNo1688 picture ID; it is recommended to carry `page>1` when paging, which can speed up the response; choose one of three `imageUrl` and `imageBase64`
keywordNoKeywords to further search in the results
imageUrlNoImage URL, maximum length 1000; only supports png/jpg/jpeg; choose one of `imageBase64`, `imageId`
pageSizeNoThe number of products per page cannot exceed 50
priceEndNoPrice filter end value (RMB), such as `100`
priceStartNoPrice filter starting value (RMB), such as `10`
imageBase64NoPure Base64 encoding, does not contain `data:image/jpeg;base64,` prefix; only supports png/jpg/jpeg; choose one of `imageUrl` and `imageId`
productCollectionIdNoOne cross-border product collection ID from the allowed values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"Filter conditions, multiple conditions separated by commas; see the table below for valid values"New value: +"Comma-separated filters: 1688Selection, certifiedFactory, totalEpScoreLv1, totalEpScoreLv2, totalEpScoreLv3, totalEpScoreLv4, qrr0, qrr1, qrr5, qrr10, shipInToday, shipIn24Hours, shipIn48Hours, noReason7DReturn, isOnePsale, isOnePsaleFreePost, new7, new30, isQqyx, JPFL, USFL, KRFL, VNFL, SAFL, RUFL, KZFL, HKFL, MOFL, TWFL."
    • addedInput schema / properties / imageUrl / maxLength
      Added value: +1000
    • addedInput schema / properties / page / minimum
      Added value: +1
    • addedInput schema / properties / pageSize / maximum
      Added value: +50
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
    • changedInput schema / properties / productCollectionId / description
      Previous value: -"Pallet ID, single choice; see the table below for valid values"New value: +"One cross-border product collection ID from the allowed values."
    • addedInput schema / properties / productCollectionId / enum
      Added value: +[
+  "262105288",
+  "262105286",
+  "262105253",
+  "262105281",
+  "262105280",
+  "262105277",
+  "262105276",
+  "262105274",
+  "262105269",
+  "262185282"
+]
    • changedInput schema / properties / sort / default
      Previous value: -{
-  "monthSold": "desc"
-}New value: +"{\"monthSold\":\"desc\"}"
    • changedInput schema / properties / sort / description
      Previous value: -"JSON format `{sort field: sorting method}`; valid fields are `price`, `monthSold`, `rePurchaseRate`"New value: +"JSON-encoded string: price, rePurchaseRate, or monthSold with asc or desc."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The one genuinely additive line is that direct API calls skip the 'Skill image conversion step', which warns of a preprocessing difference not encoded in annotations, but return shape, result volume, and paging behavior are left undisclosed.

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 the resource identified up front and no filler. The second sentence about the Skill conversion step is slightly opaque in phrasing but still carries real information, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no output schema, and annotations covering only safety, the description is minimal but the schema does heavy lifting on inputs. What is missing is the nature of the returned data (product list for sourcing?) and a disambiguation from the near-identical sibling tool — both material for an agent choosing and interpreting this call.

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?

Schema description coverage is 100%, so every parameter (page, sort, filter, priceStart/priceEnd, productCollectionId enum, etc.) is already documented in the schema. The description only restates the three mutually exclusive image-input options, adding no format, precedence, or default guidance beyond what the schema provides; baseline 3 applies.

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 and resource (image Search over 1688 Sourcing data) and states the accepted inputs, so the agent knows it retrieves 1688 products from an image. However, it never distinguishes itself from the very similarly named sibling nexscope_1688_search_by_image, leaving ambiguity about which image-search tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is input-mechanics ('Supply a JPEG/PNG image URL, pure Base64, or a returned imageId'), which the schema already covers. There is no statement of when to use this versus nexscope_1688_search_by_image, nexscope_1688_product_search, or the TikTok/CJ/Temu image-search siblings, and no exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nexscope toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources