Skip to main content
Glama

Order: Start Payment Flow

create_order_payment_link
Destructive

[Order] [What it does] Generates authenticated DSers Checkout links for awaiting-payment orders. A successful call returns only aggregate checkout_urls and message; AliExpress and Alibaba.com also return dsers_order_ids. It never charges the user or completes payment. [When to use] Use it when the user wants to pay specific awaiting-payment orders, and when the agent needs to hand the user a payment entry point for orders already in that state. Trigger words: pay these orders, create a payment link, settle this batch. [When not to use] To find awaiting-payment orders, use list_orders. To place orders with suppliers, use place_orders_to_suppliers. It cannot pay on the user's behalf. [How to use]

  • supplier_platform_id and selection_mode are required. Selected mode needs exact order IDs, up to 100; filtered mode covers every order matching the filters, which is usually far broader than the user expects, so confirm the scope first.

  • AliExpress and Alibaba.com merge selected or filtered matches into one direct checkout URL and return those dsers_order_ids. Filtered mode is capped at 100 matching orders; more than 100 is rejected.

  • The non-AliExpress path creates a persistent payment-link record and is not idempotent, so never recreate an uncertain link; verify through the order list or the Payment Link page instead.

  • The response does not return amounts, currencies, or per-group statuses. For non-AliExpress suppliers, checkout_urls contains only definitely created links and message reports whether every supplier group produced a link or the result is partial. If no link is definitely confirmed, the Tool returns a structured error. Never infer omitted group outcomes or automatically retry.

  • Read current order data before confirmation to show the exact order scope and any available amounts or currencies. The user has to open the link to pay, and payment status must be confirmed later from the order data. [Side effects] No charge; non-AliExpress groups create payment-link records. [Confirmation] Required but skippable; before calling, show the order scope and any available amounts from current order data.

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>"
    },
    "name": "create_order_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoOptional DSers order color flags. Paste JSON example: ["red"].
queryNoOptional order-table search value used in filtered mode. Required when search_by is not default.
end_timeNoOptional seller-order creation end time as a Unix timestamp for filtered mode.
place_byNoOptional existing supplier-order placement-source filter.any
countriesNoOptional destination country codes for filtered mode. This is the only country filter. Paste JSON example: ["US"].
search_byNoHow query is interpreted in filtered mode.default
agency_idsNoOptional agency IDs as decimal strings. Paste JSON example: ["100071"].
start_timeNoOptional seller-order creation start time as a Unix timestamp for filtered mode.
selection_modeYesselected uses the explicit dsers_order_ids array; filtered matches awaiting-payment orders by dsers_store_ids, query, search_by, start_time, end_time, countries, flags, agency_ids, and place_by. AliExpress and Alibaba.com accept both modes and merge matches into one checkout URL; filtered fails if more than 100 orders match.
dsers_order_idsNoExact DSers order IDs. Copy from list_orders results. Required for selected mode; omit in filtered mode. For AliExpress and Alibaba.com, selected and filtered matches are combined into one direct checkout URL. Paste JSON example: ["2088507008557908224"].
dsers_store_idsNoOptional DSers store IDs included in filtered mode. Paste JSON example: ["1999323491106619392"].
supplier_platform_idYesSupplier platform represented by the current DSers Orders tab. Copy from list_stores supplier_apps[].supplier_platform_id or list_orders; never guess it. Required for both modes, and every selected order is revalidated against it.

Output Schema

NameRequiredDescriptionDefault
messageYesRequired next step; this Tool did not charge the user
checkout_urlsYesDSers Checkout URLs ready for the authenticated user to open
dsers_order_idsNoDSers order IDs included in the AliExpress or Alibaba.com checkout 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.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the non-AliExpress path creates persistent payment-link records and is not idempotent, that partial results can occur, and that a structured error is returned when no link is confirmed. The instruction not to auto-retry or infer omitted group outcomes is valuable context. It is slightly weaker on how the destructiveHint=true annotation should be read relative to 'no charge' side effects.

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?

It is long, but the bracketed sections make it front-loaded and scannable. For a 12-parameter tool with non-obvious mode semantics and non-idempotency risk, the length is largely justified, though a few bullets (e.g., the confirmation restatement) could be tightened.

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 tool's complexity, the description covers return-value shape (`checkout_urls`, `message`, optional `dsers_order_ids`), error behavior, non-idempotency, and confirmation requirements. An output schema exists, yet the description still clarifies what is not returned (amounts, currencies, per-group statuses), which is exactly the kind of missing-by-design detail an agent needs.

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 already covers all 12 parameters, but the description adds real meaning: it explains the interplay between selection_mode and filtrable fields, the 100-order cap in filtered mode for AliExpress/Alibaba.com, the merge behavior into one checkout URL, and the revalidation of selected orders against supplier_platform_id. This goes beyond the field-level schema text.

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 opens with a specific verb and resource: it generates authenticated DSers Checkout links for awaiting-payment orders, and it explicitly says it never charges the user or completes payment. It further distinguishes itself from siblings by naming list_orders and place_orders_to_suppliers with their distinct roles.

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?

It contains an explicit '[When to use]' section with trigger phrases, and a '[When not to use]' section naming the alternatives for finding orders and placing supplier orders. It also states a precondition: orders must already be awaiting payment.

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.