Skip to main content
Glama

Order: Place Orders with Supplier

place_orders_to_suppliers
Destructive

[Order] [What it does] For AliExpress (supplier_platform_id=159831080), returns only a DSers Orders page url for the selected orders or filters so the user can continue there; no orders are placed by this call. For every other supplier, submits matching orders as an asynchronous task that may create real supplier orders and incur cost. [When to use] Use it when the user explicitly asks to place or process orders, and only after the agent has confirmed the target orders have no blockers and the user has approved. Trigger words: place these orders, send to the supplier, process pending orders. [When not to use] To check eligibility only, use the order diagnostic tool. For payment after placement, use create_order_payment_link. To read current status, use list_orders or get_order. [How to use]

  • supplier_platform_id, sales_channel_id, status, and selection_mode are required. selection_mode is selected or filtered with no default; never infer it from whether dsers_order_ids is empty.

  • supplier_account_id: Optional supplier account used to place. Only AliExpress and Alibaba.com support account selection: pass the exact supplier_account_id from current injected account context or list_stores supplier_apps[].accounts[] only when multiple usable accounts exist and the user selected one. Omit it for a single usable account and every other supplier platform. Never substitute the binding-row id, DSers user ID, email, login, alias, or name. Allowed in selected and filtered modes; it is not a search filter. AliExpress URL hand-off rejects this field.

  • selected uses exact dsers_order_ids and only the required status, supplier_platform_id, and sales_channel_id. Empty, search_by=default, and cancel_source=any count as omitted; any other search filter is rejected. IDs must be unique positive decimals; duplicates are not silently dropped.

  • Do not pass supplier_account_id for AliExpress; that path only returns a URL and rejects the field.

  • For AliExpress, selected accepts 1–20 IDs and checks ownership, sales_channel_id, supplier, and the requested status tab before returning the link. filtered checks that the selected stores belong to the account. Both modes return only a DSers Orders page url for the selected orders or filters; no order is placed.

  • For every other supplier, selected accepts 1–20 IDs and writes them as exact order_ids. One ID is checked for ownership, supplier, requested status tab, and store scope, and that order's store is pinned under sales_channel_id. The call fails if the order is not on that supplier and tab. With two or more IDs, missing or unowned IDs are skipped when collecting stores, every owned order must belong to sales_channel_id, the original unique IDs are passed through, and the call fails if none are owned. An accepted request does not guarantee successful placement; check the task result.

  • filtered omits dsers_order_ids and matches by dsers_store_ids, query, search_by, time, countries, flags, agency_ids, and cancel_source. Never approximate a few user-named orders with filters: a filter usually matches far more orders than intended and can place unwanted ones. A non-default search_by requires query; the AliExpress URL path does not support email.

  • A non-AliExpress response returns task_type and task_id; these identify the polling scope and do not mean every order was placed successfully. Poll get_job_status until terminal=true, then confirm the real outcome order by order with list_orders. If a status is unchanged or unknown, never send the placement request again, or orders may be placed twice. [Side effects] The AliExpress URL hand-off saves the order selection for continuing in DSers but does not place orders. Other suppliers may create real supplier orders and spend money. [Confirmation] Mandatory and not skippable; show each order and amount.

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": {
      "selection_mode": "<selection_mode>",
      "supplier_platform_id": "<supplier_platform_id>",
      "sales_channel_id": "<sales_channel_id>",
      "status": "<status>"
    },
    "name": "place_orders_to_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoOptional DSers order color flags for filtered mode. Paste JSON example: ["red"].
queryNoOptional order-table search value for filtered mode. Required when search_by is not default.
statusYesRequired order-tab filter used in both selected and filtered modes. AliExpress validates it before saving the selected IDs or filters; filtered mode also saves the selected tab.
end_timeNoOptional seller-order creation end time as a Unix timestamp for filtered mode.
countriesNoOptional destination country codes for filtered mode. Paste JSON example: ["US"].
search_byNoHow query is interpreted in filtered mode. Exact DSers order IDs use selection_mode=selected, not this field. For AliExpress, email is not supported.default
agency_idsNoOptional agency IDs as decimal strings for filtered mode. Paste JSON example: ["100071"].
start_timeNoOptional seller-order creation start time as a Unix timestamp for filtered mode.
cancel_sourceNoOptional cancellation-source filter for filtered mode. Exclusive of selected mode. any is treated as omitted.any
selection_modeYesRequired. selected uses dsers_order_ids; filtered uses search filters. No default; do not infer from an empty ID list.
dsers_order_idsNoExact DSers order IDs for selected mode; omit in filtered mode. Non-AliExpress placement accepts 1–20 IDs. One ID is checked for ownership, supplier, requested status tab, and store scope; with two or more IDs, missing or unowned orders are skipped when stores are collected, every owned order must belong to sales_channel_id, and the original unique IDs are dispatched. AliExpress accepts 1–20 IDs, checks ownership, sales_channel_id, supplier, and status tab, then returns a DSers Orders page URL for those orders without placing them. Copy from list_orders or get_order. Paste JSON example: ["2088507008557908224"].
dsers_store_idsNoOptional DSers store IDs for filtered mode. Every ID must belong to sales_channel_id. An omitted list resolves to every owned store under that sales_channel_id. Exclusive of selected mode. Paste JSON example: ["1999323491106619392"].
sales_channel_idYesRequired seller sales channel. Copy from list_stores stores[].sales_channel_id. Scopes dsers_store_ids in filtered mode. Selected place with one ID pins that order's store under this channel.
supplier_account_idNoOptional supplier account used to place. Only AliExpress and Alibaba.com support account selection: pass the exact supplier_account_id from current injected account context or list_stores supplier_apps[].accounts[] only when multiple usable accounts exist and the user selected one. Omit it for a single usable account and every other supplier platform. Never substitute the binding-row id, DSers user ID, email, login, alias, or name. Allowed in selected and filtered modes; it is not a search filter. AliExpress URL hand-off rejects this field.
supplier_platform_idYesCopy from list_stores supplier_apps[].supplier_platform_id or list_orders results. Required on both modes. AliExpress is 159831080.

Output Schema

NameRequiredDescriptionDefault
urlNoDSers Orders page URL for continuing with the selected orders or filters. Open it unchanged. Present only for mcp callers on AliExpress (159831080); a URL means no order was placed
task_idNoPlace-order task ID returned by DSers; copy it to get_job_status. Omitted when returning a navigation URL
task_typeNoFixed value order_process when an async place-order task was dispatched; omitted when returning a navigation URL
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructive/openWorld/non-idempotent, but the description adds substantially more: which path spends money, that an accepted request does not guarantee placement, that `task_type`/`task_id` only scope polling, that the agent must poll `get_job_status` to `terminal=true` and verify per order with `list_orders`, and that resending after an unknown status risks double placement. The mandatory, non-skippable confirmation with per-order amounts is also disclosed.

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?

Front-loaded with labeled sections ([What it does], [When to use], [When not to use], [How to use], [Side effects], [Confirmation]) and the destructive split is stated first. It is long, and the AliExpress "no orders are placed, only a URL" point is repeated three times, which costs it a point, but the length is largely earned by the branching behavior.

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?

For a 15-parameter destructive async tool, the description covers confirmation requirements, cost risk, mode-dependent validation, async task semantics, polling scope, and the double-placement hazard, so an agent can call it safely without external knowledge. Return values are left to the output schema, as expected.

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

Parameters5/5

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

Schema coverage is 100% and the schema text is unusually rich, so the baseline would be 3, but the description still adds cross-parameter rules the schema states only in isolation: selection_mode must never be inferred from an empty `dsers_order_ids`, `supplier_account_id` is rejected on the AliExpress path, it is not a search filter, and selected-mode requests must not carry search filters (empty, `search_by=default`, `cancel_source=any` count as omitted).

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?

States a specific verb and resource ("submits matching orders as an asynchronous task") and immediately splits the behavior into two distinct paths: AliExpress returns only a DSers Orders page `url` with no placement, while every other supplier creates real supplier orders. This is far more than a restatement of the name and lets an agent distinguish it from list_orders, get_order, or the diagnostic tool.

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?

Explicit when-to-use ("user explicitly asks to place or process orders", after blockers confirmed and user approval) plus trigger words, plus an explicit when-not-to-use block routing to the order diagnostic tool, `create_order_payment_link`, `list_orders`, and `get_order`. It also warns against approximating named orders with filters, which is exactly the misuse an agent would otherwise commit.

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.