Skip to main content
Glama

Nexscope Ecommerce Data MCP

1688 Order List

nexscope_data_alibaba1688_order_list
Read-only

List one page of the current buyer's 1688 orders. Current and historical tables are paged separately. Uses the currently authenticated Nexscope user's 1688 buyer authorization. Orders are read live through the existing 1688 connection. The buyer identity comes from the server, and results are not cached.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nexscope_data_alibaba1688_order_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
isHisNo
pageSizeNo
orderStatusNo
productNameNo
refundStatusNo
createEndTimeNo
modifyEndTimeNo
sellerLoginIdNo
sellerMemberIdNo
createStartTimeNo
modifyStartTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so safety is covered. The description still adds real value by disclosing that data is read live through an existing 1688 connection, is not cached, and that buyer identity is server-derived rather than passed in — useful auth and freshness context. It stops short of describing result volume, pagination limits, or failure modes when authorization is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the core action, but two sentences say the same thing about identity ("Uses the currently authenticated Nexscope user's 1688 buyer authorization" and "The buyer identity comes from the server"). That duplication wastes space that could have gone to parameter semantics.

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

Completeness2/5

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

For a 12-parameter, zero-coverage, no-output-schema listing tool, the description should at minimum explain the key filters and paging behavior. It covers the read-only/live-read profile but leaves every filter parameter and the response shape entirely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Twelve parameters with 0% schema description coverage, and the description explains none of them — isHis, orderStatus, refundStatus, the four time-boundary fields, sellerMemberId versus sellerLoginId, and the pageSize cap of 20 are all left undocumented. Only the current-versus-historical paging split is obliquely covered. This is a serious gap for a 12-parameter filter surface.

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?

States a specific verb and resource: "List one page of the current buyer's 1688 orders." It scopes the result to the authenticated buyer, but never distinguishes itself from siblings such as order_detail or order_status, so an agent must infer which to use.

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 note that "Current and historical tables are paged separately" hints at the isHis distinction, but there is no explicit when-to-use, when-not-to-use, or named alternative among the order_detail/order_status siblings. An agent gets no routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources