Skip to main content
Glama

Order: Update Details

update_order_information
Destructive

[Order] [What it does] Updates fields still editable on a DSers order in its current status — shipping address, DSers-only note, sales-channel note, supplier order message, and/or the selected supplier-row shipping method — without changing payment status, quantities, supplier product, fulfillment Variant, or mapping. [When to use] Use when the user explicitly provides new address, contact, note, or shipping-method values and the target is still editable. [When not to use] To change which supplier product or fulfillment Variant fulfills the order, use update_order_supplier. Freight can be changed only on an unplaced, canceled, or failed supplier row; a fulfilled item cannot be edited. Never guess or infer address or contact details. Do not invent a freight amount other than the documented omitted default of 0. [How to use] address fields are partial; omitted fields are preserved, so provide at least one field to change. supplier_platform_id is required only when setting sales_order_sales_channel_note or dsers_supplier_order_message, using the exact platform ID from this order, or 0 for Unmapped. freight requires service_id and company copied from list_supplier_product_shipping_methods_and_cost quotes[]. Omitted currency defaults to USD; omitted amount defaults to 0. Other omitted freight fields are written empty and clear origin, destination, tracking, transit time, and replenish. supplier_order_item_id is required with freight; copy only that ID from get_order items[].suppliers[].supplier_order_item_id. The Tool loads all current order items and supplier rows internally to resolve its owning line item. Address and freight may be sent together, but any copied quote must match the destination that will exist after this call. Show the before/after diff, including shipping method and cost (including a 0 default), and get explicit confirmation before writing. If the outcome is unknown, re-read the order rather than retry. [Side effects] Changes order details and selected supplier freight, which can affect fulfillment cost and delivery. Omitting freight amount writes 0. [Confirmation] Required, never skippable: show the diff and get explicit confirmation for exactly the specified fields, including freight cost when freight is present.

Input Schema

NameRequiredDescriptionDefault
addressNoOptional partial shipping-address update. Provide at least one field; all omitted fields are preserved. The complete patched address is checked against one supplier's rules, selected from all order items: AliExpress 159831080 if present, otherwise the lowest positive supplier platform ID, or AliExpress when all items are unmapped. This selection is independent of the supplier_platform_id used for order messages. Paste JSON example: {"sales_order_destination_city":"Los Angeles","sales_order_destination_country_code":"US","sales_order_destination_postal_code":"90001","sales_order_destination_province":"California"}.
freightNoOptional supplier-row shipping-method update. service_id and company are required. Omitted currency defaults to USD; omitted amount defaults to 0. Other omitted fields are written empty. Paste JSON example: {"amount":"4.50","company":"AliExpress Standard Shipping","currency":"USD","max_days":15,"min_days":7,"service_id":"CAINIAO_STANDARD","ship_from":"CN","ship_to":"US","tracking":true}.
dsers_order_idYesExactly one DSers order ID returned by list_orders.
supplier_platform_idNoRequired when sales_order_sales_channel_note or dsers_supplier_order_message is supplied. Copy a positive supplier platform ID from this exact order, or the exact string 0 only for Unmapped.
sales_order_dsers_noteNoOptional DSers note stored on the sales order. Empty clears it; omit to preserve it.
supplier_order_item_idNoRequired when freight is supplied. Copy items[].suppliers[].supplier_order_item_id from get_order for this exact order.
dsers_supplier_order_messageNoOptional DSers-configured supplier-order message for the selected supplier platform. Empty clears it; omit to preserve it.
sales_order_sales_channel_noteNoOptional note originating from the sales-channel order and sent with supplier-order information for the selected supplier platform. Empty clears it; omit to preserve it.

Output Schema

NameRequiredDescriptionDefault
messageYesOutcome and safe next step
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?

Goes well beyond the annotations (destructive=true, readOnly=false, idempotent=false) by disclosing concrete destructive mechanics: omitted freight fields are written empty and clear origin, destination, tracking, transit time and replenish, and an omitted amount silently writes 0. It also mandates a before/after diff with explicit confirmation and advises re-reading rather than retrying on unknown outcomes. Slightly short of 5 because it does not mention permission/scope requirements or failure modes from the address-rule validation beyond the schema's own note.

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?

Bracketed section labels ([What it does], [When to use], [When not to use], [How to use], [Side effects], [Confirmation]) make it skimmable and the purpose is front-loaded. It is long, and some sentences duplicate the schema's own default/required documentation, but the density is defensible for a destructive multi-mode mutation.

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 an 8-parameter destructive mutation with nested address/freight objects, the description covers all three modes, the value-sourcing path for dependent fields, side effects, confirmation protocol, and recovery behavior. Return values are covered by the output schema, so no further explanation is needed.

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?

Schema coverage is already 100%, so the description is not obligated to explain fields; nonetheless it adds genuine cross-parameter meaning — `supplier_platform_id` is needed only for the two note fields, `freight` requires `supplier_order_item_id` copied from `get_order`, and `service_id`/`company` must come from `list_supplier_product_shipping_methods_and_cost` quotes[]. Some of this (USD default, amount default 0) is a verbatim restatement of the schema, which caps it below 5.

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 (updates) and enumerates exactly which fields are mutable — shipping address, DSers note, sales-channel note, supplier order message, supplier-row shipping method — and explicitly enumerates what is NOT changed (payment status, quantities, supplier product, fulfillment Variant, mapping). This lets an agent separate it from `update_order_supplier` without opening either schema.

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?

Provides explicit when-to-use (user supplies new address/contact/note/freight values and the target is editable) and when-not-to-use with a named alternative (`update_order_supplier` for supplier product / fulfillment Variant changes). Adds exclusions ('a fulfilled item cannot be edited'), anti-hallucination rules ('Never guess or infer address or contact details'), and the constraint that any copied quote must match the post-call destination.

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.