Skip to main content
Glama
Sign In
bitroad-mcp

bitroad-mcp

by bitroadai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Seller list orders

seller_list_orders
Read-onlyIdempotent

Retrieve orders for your seller account with pagination and status filters to identify orders awaiting fulfillment, shipped, delivered, cancelled, or refunded.

Instructions

List orders placed against the bound seller's products (seller-side view), paginated. Filter by status (e.g. 'paid_awaiting_fulfillment' to find orders that need shipping). This is the seller-equivalent of orders_list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_size": "<page_size>"
    },
    "name": "seller_list_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from the previous page's next_cursor.
statusNoFilter by order status; omit for all orders.
page_sizeYesResults per page (1-100, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds useful behavioral context by mentioning pagination and the seller-side view, which clarifies the expected behavior without contradicting the annotations.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the primary purpose, then the filter example, and finally the sibling comparison. Every sentence adds value with no filler or redundancy.

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

Completeness5/5

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

Given the simple parameter set and no output schema, the description provides everything needed to call the tool correctly: the purpose, the pagination behavior, the filter usage, and the relationship to orders_list. No critical information is missing.

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

Parameters4/5

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

The schema covers all three parameters with descriptions, so the baseline is 3. The description goes beyond this by explaining the status filter with an example, adding semantic meaning to how the status parameter should be used. It doesn't add context for cursor or page_size, but those are already well described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists orders for the seller's products, using the specific verb 'List' with a clear resource and scope. It also distinguishes it from the sibling orders_list by calling it the 'seller-equivalent,' so an agent can immediately tell which tool 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 Guidelines5/5

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

The description explicitly names the alternative orders_list and positions this as its seller-side counterpart. It also provides a concrete usage example ('paid_awaiting_fulfillment' to find orders that need shipping), giving clear when-to-use guidance beyond the raw parameter schema.

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

Deploy Server

Other Tools