Skip to main content
Glama

Server Details

Official DSers MCP for AliExpress dropshipping, product sourcing, and order fulfillment. Discover products across AliExpress, Alibaba, and 1688; import them to connected Shopify, Wix, WooCommerce, and TikTok Shop stores; then edit listings, set prices, and publish. Manage supplier products and orders, coordinate fulfillment, and track shipments from your AI assistant.

Ownership verified
Status
Healthy
Uptime
13.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
dsers/dsers-mcp-server
GitHub Stars
20
Server Listing
DSers Dropshipping MCP
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 60 tools

Disambiguation4/5

Across 60 tools, most have clearly distinct resource/action scopes, and the extensive 'When not to use' guidance resolves most apparent overlaps. A few clusters remain close enough to confuse an agent without careful reading, especially AI mapping vs manual mapping apply, tracking sync vs tracking update, and the various shipping/logistics lookup tools.

Naming Consistency5/5

All tool names are snake_case and follow a predictable verb-first pattern such as get_, list_, update_, create_, apply_, and sync_. Some compound names are long, but they remain consistent and readable.

Tool Count2/5

60 tools is far above the practical 3-15 range and the surface includes many narrow read/write helpers. The broad dropshipping domain explains some breadth, but the set is still over-fragmented for reliable agent selection.

Completeness4/5

Coverage spans supplier discovery, import/pre-publish editing, publishing, managed product updates, mapping, pricing, orders, payment links, tracking, stores, and account/billing. Minor gaps such as direct deletion/unpublishing of managed store products or order refunds are not clearly present, but core lifecycle workflows are well covered.

Publisher details

Operator
DSers · Publisher source
Operator website
https://www.dsers.com/
Vendor relationship
First-party · Publisher source
Trust center
Unknown
Restrictions
OAuth 2.1 with PKCE is required. Tool access depends on the scopes granted to the DSers account; platform actions require the relevant store or supplier account to be connected in DSers. · Publisher source

Available Tools

60 tools
apply_ai_mappingMyProduct: Apply AI Mapping ResultA
Destructive
Inspect

[Store Products] [What it does] Applies one already-completed and user-confirmed AI Mapping task result to a product's live supplier variant mapping used for future fulfillment. [When to use] Use after an AI Mapping task has succeeded and the user has reviewed and confirmed the final product/supplier preview, to commit that result. [When not to use] To search AI Mapping candidates or create the mapping task, use the corresponding candidate-search or create tools. Never call this on an unconfirmed or still-running task. [How to use] task_id is required and must belong to the current account with status ProgressSuccess. The tool rechecks task ownership and status immediately before writing; if already applied, it returns without re-writing. The write is sent once — if the outcome is unknown, re-check with get_job_status/get_store_product_mapping rather than retrying. [Side effects] Changes the product's live supplier mapping used for future order fulfillment. [Confirmation] Required, never skippable: show the exact product/supplier/task preview and get an explicit second confirmation before calling.

Inputs: task_id (required). Returns: applied, message, task_id, operation, +5 more

apply_product_mappingMyProduct: Update Variant MappingA
Destructive
Inspect

[Store Products] [What it does] Changes only the active Basic/Advanced Mapping type, or applies a confirmed partial Mapping update to selected sales-product variants of one DSers-managed product. Omitted sales variants and the other Mapping mode are preserved. [When to use] Use after reading the latest state with get_store_product_mapping, inspecting the selected supplier products and variants, and obtaining explicit user confirmation for the exact changes. [When not to use] This Tool does not search for suppliers, infer relationships from names, or save unconfirmed AI Mapping suggestions. Use the supplier-search or AI-Mapping tools first when the relationship is not already known. [How to use]

  • Top-level mapping=[] changes only the active Mapping type. It preserves every sales variant, Basic and Advanced relationship, country array, Agent relationship, quantity, option, and Mapping Pool entry. Omit advanced_country_codes, basic_option_maps, and cam_id in this mode. If the requested type is already active, no upstream write is sent.

  • When top-level mapping contains variants, include each sales_product_variant_id at most once. For every submitted variant, nested mappings is the complete replacement within mapping_type and, for Advanced, the selected country scope. Omitted variants remain unchanged.

  • Nested mappings=[] deletes all Basic relationships for that submitted variant, including its last relationship. For Advanced it deletes only advanced_country_codes; when that field is omitted, only Global is deleted. [Basic Mapping]

  • mapping_type=Basic accepts concrete supplier products only; Agent mappings are not allowed. is_default=true is the main supplier; false or omitted is the backup supplier. Each sales variant may have at most one main and one backup relationship, and the complete final Basic state may use at most one main supplier product and one backup supplier product across the sales product.

  • Every submitted Basic relationship must contain the complete supplier_product_variant_options combination, including supplier options that are not driven by a sales option and are therefore treated as fixed selections. The Option-ID/value-ID combination must identify exactly one supplier variant and must match supplier_product_variant_id. Option names and value names may differ and are never used to infer the relationship.

  • basic_option_maps is an ID-based partial patch: submitted sales option/value keys add or replace pairs, omitted pairs are initially preserved, and pairs with no final Basic relationship reference are removed. Do not create artificial Option Pairs for fixed supplier options. [Advanced Mapping]

  • mapping_type=Advanced replaces only advanced_country_codes for submitted variants. Omission defaults to Global. Global is a fallback scope, remains distinct from country-specific mappings, and must not be dropped when both are configured. An identical relationship and quantity may carry multiple countries in one country array; different quantities remain separate relationships.

  • For the same sales variant and country, all concrete supplier mappings must use the same supplier platform; multiple supplier variants or products are allowed only when they belong to that platform. Mixing platforms for one sales variant/country is rejected.

  • The Agent platform is identified from the configured Agent platform ID, never a hard-coded ID. For the same sales variant and country, submit exactly one Agent ID with quantity 1. An Agent request must not include concrete supplier product or variant IDs or supplier variant options.

  • Every submitted supplier platform must be installed and enabled for Find Products for the current user. [Write safety] This Tool is not idempotent. It reads the current Mapping, builds one complete upstream state, writes once, and reads it back for verification. Never retry automatically when the write outcome is uncertain. [Side effects] Changes supplier relationships used by future supply and order fulfillment. [Confirmation] Required and never skippable: show the exact product, sales variants, country scopes, deletions, and old-to-new relationships before calling.

Inputs: mapping (required), mapping_type (required), dsers_product_id (required), cam_id, +2 more. Returns: message, update_mode, mapping_type, dsers_product_id, +2 more

cancel_supplier_orderOrder: Cancel Supplier OrdersA
Destructive
Inspect

[Order] [What it does] Requests asynchronous supplier-side cancellation for one DSers order that is in awaiting_payment or awaiting_shipment status; only one order per call. [When to use] Use when the user explicitly wants to stop a specific Agent or 1688 Dropshipping order whose latest confirmed status is awaiting_payment or awaiting_shipment. [When not to use] If status is unknown, check it with get_order first; do not call this for an order in any other status, or for any supplier other than Agent or 1688 Dropshipping. [How to use] Supply exactly one dsers_order_id from list_orders, verified via get_order, the matching required supplier_platform_id for Agent or 1688 Dropshipping, and required status copied from that order (awaiting_payment or awaiting_shipment). Ownership and tab eligibility are checked through Order Core before dispatch. A successful response contains only message: it means DSers acknowledged the asynchronous request, not that cancellation completed. Completion is confirmed only by a later get_order showing the cancelled status. Dispatch once; never auto-retry — re-read order state if the outcome is unclear. [Side effects] May cancel the order's supplier orders; destructive and critical-risk. [Confirmation] Requires explicit, non-skippable user confirmation; show the exact order, supplier, and status first. [Follow-up] After acknowledgement, verify cancellation with get_order; if rejected, report the reason and stop.

Inputs: status (required), dsers_order_id (required), supplier_platform_id (required). Returns: message, toolcall_response_at

create_pre_publish_productsImport: Add ProductsAInspect

[Import List Product] [What it does] Turns one to 10 supplier products into editable pre-publish products (the items on the DSers Import List page). [When to use] Use it when the user has picked products to import, and whenever the agent needs pre-publish products to exist before editing or publishing them. Trigger words: import this product, add to import list, save it for editing, bulk import. [When not to use] To edit an imported product, use update_pre_publish_product_content. For prices, use update_pre_publish_product_price. To list products in a store, use publish_products_to_stores. [How to use]

  • Send every product in items, including a single product. Each supplier_platform_id and supplier_product_id pair must come from the same search_supplier_products result.

  • Each item's languages is merged with the account's Product Settings languages and saved back: English is always included and counts toward the plan's language limit, and that settings change persists even if the import later fails.

  • When an item's country is omitted the previously selected import country applies, falling back to US; if the setting cannot be read the call stops without writing anything.

  • Read imported_items and failed_items item by item because a batch can partially succeed. Both result types include supplier IDs, and each request item appears in exactly one result array. A missing upstream outcome is reported as UPSTREAM_RESULT_MISSING; verify with list_pre_publish_products before retrying.

  • Do not auto-retry failures; check the reason first, such as a product that already has a pre-publish record.

  • Import List products, draft products, and pre-publish products are the same objects; when users use the old menu wording, proceed normally and answer in generic product terms rather than sending them to a page. [Side effects] Creates pre-publish products and may change account language settings. [Confirmation] Required but skippable; disclose the language-setting change.

Inputs: items (required). Returns: failed_items, imported_items, toolcall_response_at

create_shopify_shipping_profileShopify: Create Shipping ProfileAInspect

[Shopify Shipping Profile] [What it does] Creates one Shipping Profile with one zone and one custom flat rate in one exact Shopify store. Shopify only; WooCommerce, eBay, and other sales channels are rejected before the write. [When to use] Use when the user wants a new Shopify Shipping Profile before publishing products. [When not to use] Do not use it to select an existing profile; read current choices from list_stores.stores[].shipping_profiles. Do not use it for non-Shopify stores or when list_shopify_shipping_zones.shipping_zones is empty. [How to use] First call list_stores, select one exact row whose sales_channel_name equals Shopify case-insensitively, and copy its dsers_store_id. Then call list_shopify_shipping_zones for the same store, copy one or more returned shipping_zones[].country_code values into country_codes, and copy its currency exactly. Choose a zone_name that describes the selected countries, then provide the profile name, custom rate name, and non-negative amount. The service creates exactly one zone and rate. After success, call list_stores again and use the returned profile and location IDs for product publishing. This write is not idempotent; if the result is unknown, inspect Shopify and list_stores and never retry automatically. [Side effects] Creates a Shipping Profile in the selected Shopify store. [Confirmation] Requires explicit confirmation showing the store, profile, zone, countries, rate name, amount, and currency.

Inputs: amount (required), currency (required), zone_name (required), profile_name (required), +3 more. Returns: message, profile_name, dsers_store_id, toolcall_response_at

delete_pre_publish_productsImport: Delete ProductsA
Destructive
Inspect

[Import List Product] [What it does] Permanently deletes 1-20 exact Import List products by import_item_id; it never selects products by keyword or filter. [When to use] Call after the user reviews and selects exact products with list_pre_publish_products to remove; trigger words: delete import list product, clean up import list, remove pre-publish products. [When not to use] To find or narrow removal candidates, use list_pre_publish_products first. This tool does not remove products already published to a store. [How to use] Pass 1-20 exact import_item_ids copied from list_pre_publish_products. A successful response returns only the normalized import_item_ids submitted after Product BFF accepts the delete call; it does not provide per-item outcomes. If the outcome is unclear, re-check with list_pre_publish_products instead of retrying the delete. [Side effects] Permanently removes products from the Import List; irreversible. Dispatch once. [Confirmation] Requires user confirmation, skippable per policy; show the exact products before calling. [Follow-up] If the outcome is unclear, verify which products remain with list_pre_publish_products.

Inputs: import_item_ids (required). Returns: import_item_ids, toolcall_response_at

diagnose_order_issueOrder: Validate IssuesA
Read-onlyIdempotent
Inspect

[Order] [What it does] Read-only diagnosis of why DSers orders cannot be placed, paid, or fulfilled; reports per-dimension pass/fail results, non-blocking warnings, and resolutions. [When to use] Use when the user asks why an order is failing, or to check readiness before placing it with the supplier. Call this before place_orders_to_suppliers / placement to understand and resolve blockers. [When not to use] To actually place an allowed order, use the placement tool; this tool never places orders or edits data. [How to use] Exact dsers_order_ids mode and search-filter mode are mutually exclusive. Both modes require one concrete status and supplier_platform_id; all is rejected. Search mode evaluates one page of up to 100 orders. Exact IDs are looked up only in that supplier/tab pair, and a miss is per-order NOT_FOUND without retrying another supplier or tab. Other search filters cannot be combined with dsers_order_ids. search_by=dsers_order_id remains search mode. Item validation and platform-function checks use only items matching the selected supplier and tab. Only decision=allowed with complete=true conclusively permits placement — unknown or incomplete remains inconclusive even without a reported blocker. Dimensions whose checks are unavailable are reported in missing_checks, not treated as passing. fulfillable_item_ids contains supplier-orderable item IDs from the selected supplier/tab scope and supports initial placement from awaiting_order plus re-placement from cancelled and failed; seller-platform Fulfill restrictions are excluded from this supplier-ordering result. The supplier order-and-payment disable switch is evaluated per supplier_platform_id. CANNOT_ORDER_WITHOUT_SKU is evaluated for supplier apps that have unquoted items; a confirmed restriction is UNQUOTED_ORDER. AWAITING_ORDER_ITEM_PRODUCT_EMPTY_CANNOT_ORDER is evaluated for supplier apps that have zero-quantity items; a confirmed restriction is ZERO_FULFILLABLE_QUANTITY. MAX_CHAR_LEAVE_A_MESSAGE_TO_SUPPLIER is evaluated for supplier apps that have items with messages over 1000 characters; a confirmed restriction is SUPPLIER_MESSAGE_TOO_LONG. AWAITING_PAYMENT_MAKE_PAYMENT_BTN_DO_NOTHING is evaluated for all relevant supplier apps on awaiting-payment orders with zero cost; a confirmed restriction is AWAITING_PAYMENT_ZERO_COST. SHIPPING_COUNTRY_REQUIRED blocks placement when address.country is missing or blank, including a missing address; the order cannot be placed until a shipping country is configured. SHIPPING_METHOD_UNAVAILABLE is reported when no freight option is available for a mapped supplier product to the current shipping destination; it blocks placement until the supplier, product, or destination changes. SHIPPING_METHOD_REQUIRED is reported when a mapped supplier has available freight options but no shipping method is selected; a confirmed restriction blocks placement. ORDER_COST_EXCEEDS_REVENUE is a non-blocking warning when product cost plus shipping cost is strictly greater than order revenue on one complete, matching currency basis; it is omitted when those amounts cannot be compared safely and never changes decision, complete, or fulfillable_item_ids. Other platform-dependent checks that cannot be evaluated stay in missing_checks. [Side effects] Read-only; no order data changes. [Confirmation] Required per current configuration and not skippable. [Follow-up] If conclusively allowed and placement is the goal, proceed to the placement tool per its own confirmation rules; otherwise report the blocker or missing check and stop.

Inputs: status (required), supplier_platform_id (required), query, cursor, +8 more. Returns: orders, summary, checked_at, pagination, +1 more

find_feature_entryUtility: Fallback Feature SearchA
Read-onlyIdempotent
Inspect

[Fallback] [What it does] Searches the DSers feature catalog by English intent keywords only after confirming no existing DSers tool can complete the request; returns feature and application-page destinations without performing any business action. [When to use] Call only after verifying every other DSers tool cannot fulfill the request and a page entry point is needed; trigger words: feature entry, where to set up, no tool covers this, navigate to a feature. [When not to use] Do not use for product, order, or store queries that have dedicated tools (e.g. get_order, list_stores); this tool never substitutes for a business action. [How to use] Pass specific English intent keywords as query; at most 10 destinations are returned. An empty matches list is a valid result meaning no fallback destination exists. truncated=true means more matches exist beyond the limit — narrow the keywords or raise limit. [Side effects] Read-only; no data is changed. [Confirmation] No confirmation required. [Follow-up] If a match fits, explain the destination and ask whether to open its URL; if none fits, report there is no suitable destination and stop.

Inputs: query (required), limit. Returns: matches, truncated, catalog_count, matched_count, +2 more

get_account_profileAccount: Get ProfileA
Read-onlyIdempotent
Inspect

[Account] [What it does] Reads the signed-in DSers account's identity, permissions, visible subaccounts, and account settings such as timezone. [When to use] Call it when the user asks about account identity, registration, permissions, or subaccounts. Call it proactively before product, order, or store actions that need a permission check, or before resolving relative dates such as "today" or "this week", which need the account timezone. Trigger words: account, registration, subaccount / staff, permission, timezone. [When not to use] For the current subscription, Credits balance, or plan benefits use get_plan_and_credits; for billing history or invoices use get_plan_and_credit_billing. It cannot read accounts outside your own account tree, and never modifies permissions or subaccounts. [How to use]

  • Empty values carry meaning: an empty subaccount list means it is not visible to the current identity, and an empty menu list means a main account with full access; neither means "none".

  • Convert every time to the account timezone: returned times are UTC, and the response timestamp marks data freshness only, not registration, login, or last-modified time.

  • Partial gaps are not failures: when optional parts are missing, the rest is still reliable, so note what is missing instead of retrying or erroring out.

  • Do not surface raw data: the email address is never returned, only its verification status; store permissions are store IDs, so look up names separately. [Side effects] Read-only. No account data or permission is changed. [Confirmation] None required, the tool is read-only.

Inputs: no named parameters. Returns: nickname, timezone, permissions, account_type, +7 more

get_job_statusJob: Get Task StatusA
Read-onlyIdempotent
Inspect

[SystemInternal] [What it does] Reads the latest status of one asynchronous task created by a DSers business write tool, using the exact task_type and task_id returned by that creating tool. [When to use] Use when the user asks whether an earlier async action has finished or what stage it is at. [When not to use] Never use this to create, cancel, or rerun a task; it is read-only status only. Legacy job_id queries are unsupported, and only one task can be queried per call. [How to use] Copy task_type and task_id exactly from the creating Tool. delay_seconds is optional (default 3, max 20). terminal=true means polling can stop, but still inspect status and error. When status is unknown, never automatically retry the original write; verify the business entity instead. Product push, price sync, AI mapping, and supply-order sync actively refresh upstream state; stock sync only confirms receipt. The current or final task-specific business outcome is carried in result. For order_process, copy the task ID returned by place_orders_to_suppliers. [Side effects] None; read-only and never creates, cancels, or retries a business write. [Confirmation] Not required.

Inputs: task_id (required), task_type (required), delay_seconds. Returns: error, total, result, status, +9 more

get_managed_store_productMyProduct: Get DetailA
Read-onlyIdempotent
Inspect

[Store Products] [What it does] Reads one DSers-managed Sales Product's options and variants, mapped Supplier Products, primary and secondary supplier-variant mappings, effective supplier inventory, blacklist state, sales-channel deletion state, and sync settings. [When to use] Use it when the user asks about one managed product's variants, inventory, pricing, mapped supplier products, or sync state, and when exact IDs are needed before a price, stock, mapping, or supplier-detail operation. [When not to use] To find, filter, or count products, use list_managed_store_products. For mapped Supplier Product content or shipping data, call get_supplier_product with the paired IDs from mapped_supplier_product_list. [How to use]

  • Copy dsers_product_id from list_managed_store_products items[].dsers_product_id; it is not a Sales Product or Supplier Product ID.

  • include_sales_product_description defaults to false, so sales_product_description is omitted unless explicitly requested because descriptions can be large.

  • Each mapped_supplier_product_list[] entry provides the supplier_platform_id and supplier_product_id pair required by get_supplier_product.

  • primary_supplier_product_variant_mapping_list contains the default Basic Mapping supplier or the single supplier Product BFF can resolve for that sales variant. secondary_supplier_product_variant_mapping_list contains the non-default supplier returned only for Basic Mapping.

  • supplier_product_variant_display_price_amount is converted toward the DSers store default currency; always read it with supplier_product_variant_display_price_currency because Product BFF falls back to the supplier currency if conversion fails.

  • sales_product_variant_effective_supplier_inventory_list[].sales_product_variant_effective_supplier_inventory_quantity is Product BFF's final display inventory for the sales variant: primary stock first, but secondary stock is used when primary stock is zero or missing. It is not sales-channel inventory and cannot be attributed to one fixed Supplier Variant.

  • mapped_supplier_product_count of 0 means no mapped supplier summary was returned. sales_product_is_blacklisted_in_dsers comes from Product BFF is_unable; it is distinct from deletion on the sales channel. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: dsers_store_id (required), dsers_product_id (required), include_sales_product_description. Returns: dsers_store_id, dsers_product_id, sales_channel_id, sales_product_url, +22 more

get_orderOrder: Get DetailA
Read-onlyIdempotent
Inspect

[Order] [What it does] Reads the details of one DSers order: line items, costs and income, supplier rows, tracking numbers, and the currently saved shipping address and recipient details. [When to use] Use it when the user asks for full order detail, when inspecting Failed or cancelled orders, or when row-level detail is required to repair a blocker, edit an order, or fulfill it. Ordinary Awaiting Order placement uses list_orders summaries and diagnose_order_issue without routine per-order detail reads. Trigger words: this order's detail, its supplier order, what happened with this order. [When not to use] To find orders or see pending volume, use list_orders. To place orders, use place_orders_to_suppliers. For package movement, use get_package_details. It changes nothing. [How to use]

  • dsers_order_id is required and must be the DSers internal order ID from list_orders; a storefront or supplier order number cannot be passed directly.

  • The supplied supplier and tab identify the order to read. The returned items can include items under other suppliers or tabs. If the order details cannot be retrieved, the call returns an error such as NOT_FOUND. Treat omitted optional fields as unavailable, not as zero.

  • supplier_platform_id and tab_status stay required. Copy them from the same list_orders request when that call included them. When list_orders omitted supplier_platform_id or status, copy the omitted field from the same line_items[] row being inspected. Mixed tab_statuses: pick the tab matching the user intent, else the first known value. Do not invent pairs. If tab_statuses is empty, do not call this Tool; re-list with an explicit status.

  • items[].tab_statuses lists only the known memberships for that item. items[].mixed_tab_status=true means more than one known tab; false does not prove completeness.

  • Money uses different bases: income is authoritative in the seller-platform currency, the setting-currency figure may appear only as a labeled conversion, and item prices and supplier costs use the DSers default currency, so never mix them.

  • order.address returns the currently saved shipping address and recipient details, including street address lines, name, phone, email, tax ID, passport numbers, company, and birthday when populated. sales_order_recipient_birthday is returned exactly as stored; AliExpress Brazil rules use DDMMYYYY. Values are returned as stored, without masking; empty fields are omitted. An omitted component does not prove the address is complete or placeable; use diagnose_order_issue before placement. Product titles must be shown verbatim, never translated or truncated. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: tab_status (required), dsers_order_id (required), supplier_platform_id (required). Returns: order, toolcall_response_at

get_package_detailsTracking: Get EventsA
Read-onlyIdempotent
Inspect

[Tracking / Logistics] [What it does] Reads the logistics status, attention flag, and carrier event snapshot that DSers holds for one tracking number on the authenticated account. [When to use] Use it when the user asks where a shipment is or why it has stalled, and whenever the agent needs event evidence before handling a delivery exception or replying to a buyer. Trigger words: where is my package, check this tracking number, delivery exception, when will it arrive. [When not to use] It looks up tracking numbers only and cannot return every package on an order; get the tracking number from get_order first. To write a tracking number back to a store order, use sync_existing_tracking_numbers_to_store. External numbers outside this account cannot be queried. [How to use]

  • tracking_number is required and must belong to this account; a number supplied by a buyer cannot be looked up directly.

  • Events are not necessarily newest first; compare timestamps to identify the latest checkpoint.

  • Event times use the carrier's own format; a normalized timestamp and timezone appear only when available, so confirm the timezone before comparing times.

  • An empty event list is a valid result meaning no scans yet; it does not prove the parcel is unshipped or lost. Estimated delivery is not returned and must not be inferred.

  • The data is a stored DSers snapshot that can lag the carrier site. The attention flag is only a marker, not a confirmed exception. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: tracking_number (required). Returns: events, attention, tracking_status, toolcall_response_at

get_plan_and_credit_billingPlan/Credits: Search Billing HistoryA
Read-onlyIdempotent
Inspect

[Subscribe/Credits] [What it does] Returns exactly one billing result selected by billing_kind: subscription_billing (paid recurring and one-time subscription purchase records), credit_usage (AI Credits consumption history), or invoice_download (one invoice download URL). [When to use] Use when the user wants to see subscription payment history, AI Credits usage history, or download an invoice. [When not to use] For the current plan or Credits balance, use get_plan_and_credits. For order-level billing, use get_order_paymentlink_and_billing. This tool never creates a payment, changes a subscription, or recharges Credits. [How to use] billing_kind is required and selects exactly one mode per call. Each mode accepts only its own fields: subscription_billing uses start_time/end_time/billing_id/sort_by/pagination; credit_usage uses granularity/model/pagination; invoice_download uses only billing_id and invoice_id. subscription_billing is server-fixed to paid DSers subscription and one-time-purchase records only. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: billing_kind (required), model, sort_by, end_time, +6 more. Returns: billing_kind, credit_usage, invoice_download, toolcall_response_at, +1 more

get_plan_and_creditsAccount: Get Plan Benefits & AI CreditsA
Read-onlyIdempotent
Inspect

[Subscribe/Credits] [What it does] Reads the current account's subscription plan, plan limits/benefits, and current AI Credits balance in one call. [When to use] Use when the user asks about their current plan, what the plan includes, or their remaining AI Credits. Trigger words: my plan, plan benefits, Credits balance. [When not to use] For identity or permissions, use get_account_profile. For billing history or invoices, use get_plan_and_credit_billing. This tool returns no usage history or billing line items. [How to use] No inputs are required; call with an empty object. benefits are plan allowances and feature switches, not current usage. credit_balance has subscription_credits, lifetime_credits, and an authoritative total_credits; never sum the first two to replace it. current_subscription is only the current snapshot, not full subscription history. All required upstream reads must succeed together; if any fails, the whole call returns a retryable error instead of partial data. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: no named parameters. Returns: benefits, credit_balance, active_subscriptions, current_subscription, +1 more

get_pre_publish_productImport: Get Item DetailA
Read-onlyIdempotent
Inspect

[Import List Product] [What it does] Reads the editable snapshot of one pre-publish product — an item on the DSers Import List page: supplier product/platform IDs, content, images, package details, options, variants, prices, stock, and the resource_version required by content and price edits. [When to use] Use it when the user asks for one pre-publish product's full detail, and whenever the agent must obtain the current version and row identifiers before editing or repricing it. Trigger words: this pre-publish product, this item in my import list, its variants, check before editing. [When not to use] To find or filter pre-publish products, use list_pre_publish_products. For a product already pushed to a store, including Draft status, use get_managed_store_product. It changes nothing. [How to use]

  • import_item_id is required and comes from list_pre_publish_products items[].import_item_id.

  • The response item.supplier_product_id and item.supplier_platform_id identify the original supplier product and platform; copy them exactly when another supplier-product Tool requires the pair.

  • include_supplier_product_description defaults to false, so both supplier_product_specifications (SPECIFICATIONS) and supplier_product_description (description body) are omitted unless explicitly requested because descriptions can be large. Set it to true to read both sections; each is returned separately without merging or rewriting the source content.

  • resource_version is the token for content edits and price edits, and it expires after each such write; re-read immediately before those writes instead of reusing an older value.

  • supplier_product_variant_id and option supplier_product_option_value_id can repeat because duplicated rows keep their supplier ID, so always pair them with variant_index or value_index.

  • Prices and costs are exact strings; send them back unchanged and never recompute or round them. Currency is reported at item and variant level.

  • If a write's outcome is unclear, re-read with this tool to confirm the current state rather than retrying the write.

  • Import List products, draft products, and pre-publish products name the same objects; accept the old wording and answer in generic product terms rather than sending the user to a page. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: import_item_id (required), include_supplier_product_description. Returns: item, package, resource_version, toolcall_response_at, +3 more

get_pre_publish_product_organizationImport: Get Organization & Category ChoicesA
Read-onlyIdempotent
Inspect

[Import List Product] [What it does] Reads current and available Organization and Category values for pre-publish products in one target store. Organization includes Collection, Type, Tags, and Vendor. [When to use] Use it when the user wants to inspect or change category, collection, tags, vendor, or URL settings before publishing. It is the normal read-and-review step before update_pre_publish_product_organization; call that Tool only when the user chooses a change. It is optional when no Organization or Category review is needed. [When not to use] For product content and variants, use get_pre_publish_product. To save actual changes, use update_pre_publish_product_organization. It is not a prerequisite for publish_products_to_stores. [How to use]

  • import_item_ids (1 to 100) and dsers_store_id are required; send the whole selection at once. Store choices are shared and each item returns its current store-specific selections.

  • For a multi-store review, call once per store and use only choices returned for that store.

  • When organizations_truncated or categories_truncated is true, narrow with organization_name, keyword, or category_keyword and re-read.

  • categories_supported=false means the platform returned no categories. select_number=0 means no declared upper limit, and is_create controls whether new values may be created.

  • Show choices to the user before applying changes. A batch read can fail per item, so inspect each failure reason and retryable flag. [Side effects] None. [Confirmation] Not required.

Inputs: dsers_store_id (required), import_item_ids (required), keyword, marketplace_id, +2 more. Returns: items, categories, organizations, dsers_store_id, +5 more

get_pricing_rulePricing: Get Store RuleA
Read-onlyIdempotent
Inspect

[Pricing Rule] [What it does] Reads one owned store's Tool-facing Pricing Settings: the active mode (none, basic, advanced, or ai_custom), saved Basic, Advanced, and AI Custom bodies, price endings, exchange-rate context, non-blocking warnings, and the resource_version required by updates. Inactive saved rules are returned only as context. [When to use] Use when the user asks for a store's pricing formula, strategy, margins, price endings, or exchange rate, and immediately before every update_pricing_rule call. [When not to use] To save Pricing Settings, use update_pricing_rule. To calculate the price one managed product would receive, use simulate_pricing_rule. To change product prices, use the applicable product update Tool; this Tool never reprices products. [How to use]

  • Copy dsers_store_id from list_stores. Pricing Rules are store-wide; there is no account-wide or per-product rule.

  • Read mode first. Only its matching body is active. For advanced, read formula_mode: fixed uses fixed_ranges and fixed_rest, while custom uses custom_ranges and custom_rest. Other returned bodies are inactive saved rules and must not be reported as current.

  • Advanced custom formulas are view-only: report custom_ranges and custom_rest, but do not pass them to update_pricing_rule; only Advanced fixed formulas can be modified through that Tool.

  • ai_custom is separate from Advanced custom. Report ai_custom_rule only when present and use ai_custom_formula_for_user as read-only presentation.

  • When needs_initial_rule is true, the store has only an unsaved default shell. The first rule save needs a complete matching rule body, but cents or currency may still be updated independently.

  • If warnings reports an invalid saved AI Custom formula, show that warning to the user. The invalid ai_custom_rule is omitted, while Basic, Advanced, cents, currency, and resource_version remain usable.

  • Basic and Advanced range boundaries are inclusive USD decimal costs on a fixed 0.01 grid. AI Custom explicit monetary fields are USD decimals. Store currency and exchange-rate settings are returned separately and must not be used to reinterpret saved rule values.

  • Copy resource_version unchanged into the next update. After any successful update, discard the old version and read again before another change. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: dsers_store_id (required). Returns: mode, cents, currency, warnings, +12 more

get_push_shipping_recommendationPush: Get Matched Product LogisticsA
Read-onlyIdempotent
Inspect

[Import List Product] [What it does] Reads publish-time logistics candidates for each exact Import List product and target-store pair. Product Core computes these candidates from both the product's logistics conditions and the target store's current logistics settings. Results apply only to their exact target and are not a general store shipping-method list, the supplier product's complete shipping catalog, or a supplier freight quote. [When to use] Use only when actively preparing an exact publish_products_to_stores call, once for every product-store target in that request. Do not call it for standalone or exploratory shipping queries. [When not to use] Do not use it to browse store or order logistics, publish or edit products, or estimate freight, landed cost, prices, or pricing formulas. For supplier-cost workflows, including requests to build pricing formulas, use list_supplier_product_shipping_methods_and_cost. [How to use]

  • import_list_ids and dsers_store_ids expand into a unique Cartesian product capped at 100 targets; copy IDs exactly from list_pre_publish_products and the store-discovery Tool.

  • If any requested target is missing, malformed, or hits an upstream error, the entire call fails instead of returning partial results.

  • Handle each result independently by its exact import_item_id and dsers_store_id. If logistics is non-empty, present only that target's candidates and ask whether the user wants to specify one. Selecting a candidate is optional; never choose for the user unless they already specified the exact service_id for that target.

  • If the user chooses a candidate, copy its exact service_id only to the matching publish_products_to_stores items[].stores[].shipping_method_id with the same import_item_id and dsers_store_id. Do not reuse a selection for another product-store target or derive it from company_name or another source.

  • If the user declines, does not choose one, or asks to use the default logistics, omit only that target's shipping_method_id. An empty logistics array is a successful and complete result for that pair; it does not mean the supplier product itself has no shipping methods or freight quote. Do not search the web, call another Tool or API to replace the result, infer a carrier, or manufacture a shipping method. Continue publishing that target with its default logistics.

  • amount belongs only to that publish candidate and is not a general supplier freight quote. It is a decimal string in major currency units, not a float. [Side effects] None; read-only and changes no product or store logistics settings. [Confirmation] Not required. [Follow-up] Return to the current publish_products_to_stores workflow; never reuse these results for another target or workflow.

Inputs: dsers_store_ids (required), import_list_ids (required). Returns: items, toolcall_response_at

get_store_product_mappingMyProduct: Get Mapping DetailA
Read-onlyIdempotent
Inspect

[Store Products] [What it does] Reads the MCP-safe saved mapping view for one DSers-managed sales product, including Basic and Advanced variant relationships, country scopes, explicit Basic option maps, and Agent relationships. Each saved supplier-variant relationship is checked against the supplier product's current variants; an invalid Basic or Advanced relationship is omitted independently without hiding another valid relationship on the same sales variant. [When to use] Use before applying Mapping changes and whenever the user wants to inspect or verify saved relationships. [When not to use] To search candidate supplier products or generate AI Mapping suggestions, use the corresponding tools; this tool never creates or updates Mapping. Use get_managed_store_product for current prices and simulate_pricing_rule for calculated prices. [How to use] Pass dsers_product_id alone, or dsers_store_id together with sales_product_id. Public mapping_type values are Basic and Advanced. basic_option_maps exposes explicit ID relationships; names are presentation only. Country arrays retain Global alongside explicit countries because Global is a fallback, not a replacement for country-specific data. The response omits the raw pool, prices, currency, ship-from, workflow fields, and any update-version token. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: dsers_store_id, dsers_product_id, sales_product_id. Returns: MCP-safe saved mapping projection for one DSers-managed sales product.

get_supplier_productSupplier: Get Product DetailA
Read-onlyIdempotent
Inspect

[Supply Product] [What it does] Reads one supplier product's options, variants, stock, prices, shipping origins, and availability status for a given destination and language context. [When to use] Use it when the user asks about a specific supplier product's quality, stock, price, or shipping, and when the agent must verify a shortlisted candidate before importing, mapping, or quoting freight. Trigger words: this supplier product, enough stock, ships to, supply cost. [When not to use] To find candidates, use search_supplier_products. For destination freight costs, use list_supplier_product_shipping_methods_and_cost. For a product already in the store, use get_managed_store_product. [How to use]

  • Copy supplier_platform_id and supplier_product_id from the same search candidate; never use applications[].app_id or a DSers-managed product ID.

  • supplier_product_url is the usable product-detail entry; for Agent and 1688 Dropshipping it points to the configured DSers application page.

  • include_supplier_product_description defaults to false, so supplier_product_description is omitted unless explicitly requested because descriptions can be large.

  • Statuses such as NotShipTo, NotLanguage, NotDropShipping, and NotAvailable mean unavailable under the requested country or language, not that the product is missing; retry with another destination before concluding.

  • country, language, and currency are requested context only and may be unsupported upstream; report the returned values, not the requested ones.

  • Only supplier_product_variant_list[].supplier_product_variant_id is accepted for freight quotes, ordering, and mapping; stock of 0 means that variant is out of stock, not that the product is delisted.

  • Prices are strings and must be read with their currency, which can differ between variant and product level. Quotes exclude shipping, so never treat them as landed cost. [Side effects] None; read-only, and it never imports or maps a product. [Confirmation] Not required.

Inputs: supplier_product_id (required), supplier_platform_id (required), country, currency, +2 more. Returns: supplier_product_id, supplier_platform_id, supplier_product_url, toolcall_respo…

import_store_products_to_dsersMyProduct: Import from StoreAInspect

[Store Products] [What it does] Imports one to five selected seller-platform products from one connected store into DSers management; already-managed products are rejected. [When to use] Use when the merchant wants DSers to manage products that already exist in that store. [When not to use] For products already managed, browse them with list_managed_store_products instead of importing again. [How to use] Take dsers_store_id from list_stores and one to five sales_product_ids from search_store_products. The response is a completion message; this Tool exposes no fulfillment-service option or asynchronous job identifier. [Side effects] Creates DSers-managed products for the store; dispatch each import once. [Confirmation] Required; skippable per authorization policy. [Follow-up] Re-read list_managed_store_products if the merchant wants to review the imported products; otherwise report the completion message and stop.

Inputs: dsers_store_id (required), sales_product_ids (required). Returns: message, toolcall_response_at

list_managed_store_productsMyProduct: Browse Managed ProductsA
Read-onlyIdempotent
Inspect

[Store Products] [What it does] Lists one store's DSers-managed products as lightweight card-ready summaries with product identity, title, image, selling-price range, mapping status, sales status, and mapped supplier product identities, store links, and price ranges. [When to use] Use it when the user browses or filters products already managed in DSers, and when the agent needs a dsers_product_id before reading detail or changing price, stock, or mapping. Trigger words: my products, managed products, unmapped products, product list. [When not to use] For sales options or variants, exact variant IDs, mapped supplier IDs, effective supplier inventory, sync settings, DSers blacklist state, or seller-deletion state, use get_managed_store_product. For store products not yet imported into DSers, use search_store_products. This tool never edits products. [How to use]

  • dsers_store_id is required and comes from list_stores; use list_stores separately when the card also needs the store display name.

  • product_search_type changes what keyword searches: store searches Sales Product titles, supplier_product_name searches mapped Supplier Product names, and supplier_store_name searches supplier store names.

  • items[].dsers_product_id is the required DSers-managed product ID, not a supplier or sales-platform ID; use it with get_managed_store_product and Mapping Tools.

  • The current Product BFF list response does not expose sales_product_id, so this Tool does not invent it. Supplier store name and URL come from Product BFF's mapped Supplier Product summaries and remain absent when the supplier platform does not provide them.

  • Sales prices and supplier product prices are separate min/max decimal strings with their own currencies. The supplier range is product-level price data, not a normalized variant cost; never label it USD unless supplier_product_currency is actually USD.

  • items[].mapped_supplier_product_list contains Product BFF's main mapped Supplier Product summaries; Basic Mapping non-default secondary suppliers are not included.

  • counter.all is the total number of managed products, counter.unmapped is the number with no supplier Mapping, and counter.supplier_count groups mapped-product counts by configured supplier platform ID and name. Supplier platforms absent from configuration are omitted.

  • Empty items means no match, not an error. When pagination.has_more is true, pass next_cursor back unchanged as cursor and keep every filter and sort identical. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: dsers_store_id (required), cursor, keyword, order_by, +19 more. Returns: items, counter, pagination, toolcall_response_at

list_ordersOrder: Browse OrdersA
Read-onlyIdempotent
Inspect

[Order] [What it does] Browses orders, returning order summaries, per-tab counts, and cursor pagination; it is the entry point for obtaining order IDs. Set only_count=true to return only those per-tab counts with an empty orders array and no next page. An explicit supplier_platform_id limits results to that supplier; omitting it searches across suppliers. [When to use] Use it when the user wants to find orders, see pending volume, or filter by store, buyer, or time, and whenever the agent needs real order IDs before reading detail or processing. For how many orders or tab volume only, set only_count=true and read counts; do not follow with a second browse unless the user then asks for the list. Trigger words: recent orders, pending orders, this buyer's order, problem orders, how many orders. [When not to use] For Failed/cancelled inspection or order-blocker repairs, use get_order. Ordinary Awaiting Order placement uses these list summaries plus diagnose_order_issue; it does not require a detail read for every order. To place orders, use place_orders_to_suppliers. For shipment tracking, use get_package_details. [How to use]

  • only_count defaults to false. Set true only when the user asks how many orders or tab volume. Then orders is always empty and is not proof of zero orders; use counts. Empty orders must not be copied into get_order or placement. cursor, page_size, and sort_order are ignored. Do not fan out a count call into an exact order-number scan.

  • supplier_platform_id is optional. When the user names no supplier, omit it: orders and returned line items are not limited to one supplier. The string 0 searches Unmapped only and still filters items to Unmapped. Copy a positive ID from list_stores supplier_apps[].supplier_platform_id when the user names a supplier, and never substitute a sales channel ID.

  • status is optional. Omit it by default when the user does not name a tab, and for exact order-number lookup; that returns cross-tab rows within the selected supplier scope in one call. Do not fan out tabs. An explicit status filters returned line items to that tab. Statuses are tab memberships, not exclusive states: an order can sit in several tabs, counts overlap and must not be summed into a total, and pending and awaiting order are distinct values that both belong in any summary.

  • Each line_items[] row exposes supplier_platform_id and tab_statuses. If this call omitted supplier_platform_id or status, copy the omitted field from the same line_items[] row into get_order. Mixed tab_statuses: pick the tab matching the user intent, else the first known value. Do not invent supplier/tab pairs. If tab_statuses is empty, do not call get_order; re-list with an explicit status. Do not fill item tabs from orders[].order_status.

  • Each row includes dsers_store_id and, when available, sales_channel_id; resolve recognizable store and supplier names from current account context. line_items[] includes verbatim seller title, SKU when available, quantity, and known fulfillable quantity. Its supplier rows include verbatim product/variant names, quantity, selected shipping method name, and supplier order number. Missing optional fields are unavailable, not zero.

  • other_supplier_platform_count summarizes items with other suppliers. has_other_supplier_items indicates whether any exist; other_supplier_items_count lists each supplier_platform_id, its tabs, and its item count. Only positive counts are included. Use it to explain the order's additional supplier items to the user.

  • Each row's order_status is the tab requested for that call when status was set; when status was omitted it is the first known item tab, not a complete status set or an exclusive whole-order state.

  • Money is reported in several bases: order income is authoritative in the seller-platform currency, the setting-currency amount may appear only as a labeled conversion, and item prices and supplier costs use the DSers default currency. Row money follows this request's supplier filter; when supplier_platform_id is omitted, that scope is not limited to one supplier.

  • To search multiple seller order numbers, set search_by=order_no and pass a comma-separated query, for example 1001,1002 or ABC-1001,ABC-1002. English and Chinese commas are accepted. Only the first 100 non-empty keywords are searched. Results match any supplied keyword as a substring, so 1001 can also match 10010; verify returned sales_order_number values before selecting orders. When both time fields are omitted, order-number lookups search all available non-archived order history through the end of today; ordinary browsing defaults to the last 30 days. Store, supplier, status, and time filters still apply. Pass next_cursor with the same query and filters to retrieve more results. only_count=true counts orders matching the same batch filter.

  • Pages hold up to 100 rows; pass the returned cursor back unchanged for more. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: query, cursor, status, end_time, +8 more. Returns: counts, orders, pagination, toolcall_response_at

list_packagesTracking: Browse PackagesA
Read-onlyIdempotent
Inspect

[Tracking / Logistics] [What it does] Lists account-owned packages by normalized logistics status; read-only. [When to use] Use when packages that are pending, in transit, delivered, in an exception state, or flagged for attention are needed. [When not to use] For the tracking events of one known package, use get_package_details instead of this tool. [How to use] Filter with status=all, status=pending, status=in_transit, status=delivered, status=abnormal (all exception packages), or status=attention (flagged packages). You can also filter by order/tracking keyword, store, supplier platform, order age, or Unix time range; page_size caps at 100; reuse the previous next_cursor to page. An empty items array is valid; has_more=true means more results remain. [Side effects] Read-only. [Confirmation] No confirmation required. [Follow-up] If a package is in an exception or appears overdue, inspect it with get_package_details; otherwise report the result and stop.

Inputs: cursor, status, keyword, end_time, +8 more. Returns: items, counts, pagination, toolcall_response_at

list_platform_shipping_methodsSupplier: List Logistics by CountryA
Read-onlyIdempotent
Inspect

[Supplier / Logistics] [What it does] Lists logistics/shipping services available for one supplier platform and destination country (or Global). [When to use] Use when you need valid shipping_method values for a given supplier and destination, such as before update_order_supplier or a pricing calculation. [When not to use] Not for checking an order's actual shipping status; this only returns available service options. [How to use] supplier_platform_id (from list_stores) and country_code (from the countries list, a 2-3 letter code or "Global") are both required; returns each service's ID, name, average cost, and time. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: country_code (required), supplier_platform_id (required). Returns: total, logistics, toolcall_response_at

list_pre_publish_productsImport: Search ListA
Read-onlyIdempotent
Inspect

[Import List Product] [What it does] Searches the account's pre-publish products — the items on the DSers Import List page: imported from suppliers, not yet pushed to a store — returning summary rows: supplier product/platform IDs, title, supplier, cost and sell price ranges, stock, tags, and push status. [When to use] Use it when the user wants to find, browse, or filter products saved but not yet pushed to a store, and when the agent needs an import_item_id before reading detail, repricing, or pushing. Trigger words: products I saved, products in my import list, not pushed yet, pre-publish products. [When not to use] For one pre-publish product's options, variants, prices, or stock, use get_pre_publish_product. For supplier products not yet imported, use search_supplier_products. For products already on a store, including Draft status, use list_managed_store_products. It never adds, edits, or removes items. [How to use]

  • No parameter is required; with no filters it returns the default list.

  • Each row's supplier_product_id and supplier_platform_id identify the original supplier product and platform; copy them as a pair when another supplier-product Tool requires them.

  • Rows are summaries with _partial true; option, variant, per-SKU price, and stock details stay empty until you call get_pre_publish_product.

  • Cost bounds are exclusive when sent alone but inclusive when both are sent, and they use USD major units, not the store currency.

  • sku_limit is a strictly-greater-than threshold; omit it or send 0 to skip SKU-count filtering.

  • Empty items is a valid result. When has_more is true, resend next_cursor unchanged and keep filters and sort identical.

  • Import List products, draft products, and pre-publish products all name the same objects; accept the old wording and answer in generic product terms instead of sending the user to a page. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: page, sort, cursor, keyword, +16 more. Returns: items, pagination, toolcall_response_at

list_shopify_shipping_zonesShopify: List Shipping ZonesA
Read-onlyIdempotent
Inspect

[Shopify Shipping Zones] [What it does] Lists the Shopify Markets countries and regions available to one exact owned Shopify store, plus that store's currency. Shopify only; it does not list existing Shipping Profiles and it does not create or change anything. [When to use] Call after list_stores and before create_shopify_shipping_profile to obtain authoritative country_codes and currency for that exact store. [When not to use] Do not use it for non-Shopify stores, to inspect existing profiles, or to choose a custom profile name, zone name, rate name, or amount. Existing profiles come from list_stores.stores[].shipping_profiles. [How to use] Copy one exact Shopify dsers_store_id from list_stores. Select one or more returned shipping_zones[].country_code values for create_shopify_shipping_profile.country_codes, and copy the returned currency exactly. Choose a zone_name that clearly describes the selected countries. If shipping_zones is empty, stop and do not create a profile with guessed country codes. [Side effects] Read-only; no Shopify or DSers configuration is changed. [Confirmation] None required.

Inputs: dsers_store_id (required). Returns: currency, dsers_store_id, shipping_zones, toolcall_response_at

list_storesDiscover Stores and Supplier AppsA
Read-onlyIdempotent
Inspect

[Store] [What it does] Lists connected seller stores with their application, country, currency, timezone and connection status, plus supplier applications and their connected accounts. Pass view=account_context to return only stores and supplier_apps; this view omits stores[].pricing_currency, stores[].shipping_profiles, and push_configuration. Omit view or use view=full for the full response. [When to use] Call it when the user asks which stores or supplier accounts are connected, about a store's currency, timezone or status, and proactively before any store-scoped action because downstream tools accept only a store ID. Trigger words: store list, supplier account, Shopify, store status, authorization, currency, timezone. [When not to use] For products inside a store use search_store_products; for pricing-rule detail use get_pricing_rule; for a reconnect link use start_store_reauthorization. It never adds, unbinds or edits stores or supplier accounts. [How to use]

  • In most cases, omit view and use the default full response. Pass view=account_context only when you need just stores and supplier apps/accounts without pricing, Shipping Profile, or product-push details.

  • Match the user's store reference against the returned stores; continue only on one clear match, ask the user to choose on multiple matches, and never write to all stores by default.

  • An empty list means no connected store is available, and sections in degraded_parts are unavailable only this time — note them and continue rather than retrying. If a status is not AVAILABLE, inspect the returned status before choosing reauthorization; do not infer that every non-available state requires it.

  • Do not mix IDs: stores[].dsers_store_id for store-scoped tools, stores[].sales_channel_id for connection flows, supplier_apps[].supplier_platform_id for supplier scope, and supplier_apps[].accounts[].supplier_account_id for an exact supplier account. The account ID comes from upstream supplierId; it is not the account row id, user ID, email, or login name.

  • Only AliExpress and Alibaba.com support multiple supplier accounts. Pass supplier_account_id to place_orders_to_suppliers only when one of those platforms has multiple usable accounts and the user selected one; omit it for a single account and every other supplier platform.

  • Hidden stores are still returned — exclude or flag them when counting, and read each store in its own currency and timezone, not the account's.

  • For publish_products_to_stores, Shopify Shipping Profile choices come from stores[].shipping_profiles[].id and the chosen profile's locations[].id; fixed product-push choices remain in that Tool's input schema, while this Tool also returns dynamic languages and effective store defaults.

  • For a Shopify store, if stores[].shipping_profiles is empty, first call list_shopify_shipping_zones for the same store to obtain valid country codes and currency, then call create_shopify_shipping_profile. After creation succeeds, call list_stores again and use the refreshed stores[].shipping_profiles[].id and the selected profile's locations[].id; never invent or reuse stale IDs. [Side effects] Read-only; no store, authorization or push setting is changed. [Confirmation] None required; picking among matches is disambiguation.

Inputs: view. Returns: stores, supplier_apps, degraded_parts, push_configuration, +1 more

list_supplier_product_change_notificationsNotify: Supplier Product ChangesA
Read-onlyIdempotent
Inspect

[Supply Product] [What it does] Read-only list of cost, stock, SKU, and availability change notifications for previously ordered supplier products from the last 30 days. [When to use] Use to check supplier-side changes affecting mapped store products. [When not to use] For product details, use get_supplier_product; for other alert types, use the applicable notification tool. [How to use] App/store filters use decimal-string ID arrays; times use Unix timestamps; page_size caps at 100. Only changes from the last 30 days are returned; an empty result is valid. Mapped metadata can be incomplete — fields in missing_fields remain unknown. Pass next_cursor when has_more=true. [Side effects] Read-only; does not mark notifications as read. [Confirmation] No confirmation required. [Follow-up] For a cost increase needing margin review, use get_pricing_rule; for an already-approved change, use update_pricing_rule; for stockout/unavailability, find replacements with search_supplier_products; for a SKU change on a mapped product, review candidates with search_ai_mapping_candidates; otherwise report and stop.

Inputs: cursor, end_time, page_size, start_time, +6 more. Returns: items, pagination, toolcall_response_at

list_supplier_product_shipping_methods_and_costSupplier: Get Freight QuotesA
Read-onlyIdempotent
Inspect

[Supply Product] [What it does] Lists freight quotes for one specified supplier product (or specific SKUs) to a destination country, for comparing supplier shipping cost, delivery time, and tracking support, and for landed-cost calculations and product pricing before or after import. [When to use] Use when the user needs shipping costs for a specified supplier product or SKU, or wants to use freight in landed-cost, profit-margin, or selling-price calculations. [When not to use] For product or variant details, use get_supplier_product; to import, use the corresponding product import tool, not this one. To select a publish-time shipping_method_id for an exact Import List product-store target, use get_push_shipping_recommendation. [How to use] Copy supplier_platform_id and supplier_product_id from search_supplier_products or get_supplier_product; ship_to_country is a destination country code. For one SKU use supplier_product_variant_id; for several use supplier_product_variant_ids. Copy either from get_supplier_product supplier_product_variant_list[].supplier_product_variant_id, or omit both for product-level quotes. The returned quotes[].ship_from is supplier-provided information, not a selectable filter. An empty quotes list is a valid result and means the upstream returned no freight quote for the specified supplier product, SKUs, destination, and quantity. Never invent a freight amount or present an estimate as a returned quote; if the user wants an estimate, label it explicitly and obtain their confirmation. [Side effects] Read-only; no data changes. [Confirmation] No confirmation required. [Follow-up] If a quote meets cost, timing, and tracking needs, continue the original product flow; if none is available, verify the destination and SKUs or abandon the candidate.

Inputs: ship_to_country (required), supplier_product_id (required), supplier_platform_id (required), zip, +7 more. Returns: query, quotes, quote_count, toolcall_response_at

list_supplier_search_filtersSupplier: Get Search Filter OptionsA
Read-onlyIdempotent
Inspect

[Supply Product] [What it does] Returns the machine values of every supplier-product search filter available to this account, grouped by visible online supplier platform, plus which filters each platform actually supports. Returns no products. [When to use] Call before running a supplier product search, to translate spoken conditions such as "ships from the US", "arrives within 3 days", "free shipping", a category, or a specific carrier into submittable values; initial discovery can be called with no input. Pass supplier_platform_id to load one platform's options, and optionally parent_category_id to load only that category's direct children. [When not to use] Use search_supplier_products when you need actual products; this tool returns filter values only. Does not cover filters for products already imported into DSers or listed in a store. Not a settings reader — it cannot view or change the user's logistics configuration. [How to use] Copy platforms[].ship_from[].supplier_product_country_code to search ship_from, platforms[].ship_to[].supplier_product_country_code to ship_to, platforms[].categories[].supplier_platform_category_id to category_ids, platforms[].shipping_methods[].supplier_shipping_service_id to shipping_method, and filter_capabilities[].options[].value to the named search input. Labels are display-only. Every value is bound to its supplier_platform_id, and only keys listed in that platform's supported_filters take effect. A category response contains root categories or one requested parent's direct children; when has_children=true, call again with that category ID as parent_category_id. Monetary ranges are always USD. failed_sources means one filter type on one platform is missing, not a total failure — other platforms and options remain usable, and retrying only helps when retryable=true. [Side effects] None, read-only. [Confirmation] Not required. [Follow-up] After the user picks filter values, call the supplier product search tool named in next_tool.

Inputs: parent_category_id, supplier_platform_id. Returns: guidance, platforms, failed_sources, toolcall_response_at

list_supported_countriesUtility: List CountriesA
Read-onlyIdempotent
Inspect

[Utility] [What it does] Lists countries currently supported by DSers, returning each country's ID, code, and display name. [When to use] Use it to obtain valid destination country codes before calling logistics tools such as list_platform_shipping_methods. [When not to use] It does not support search, filtering, or pagination, and cannot modify country configuration. [How to use] No input is required. Copy the returned countries[].code exactly for later logistics calls; never use the country name or ID as the code. total equals the number of countries returned in this call. [Side effects] None; read-only. [Confirmation] Not required.

Inputs: no named parameters. Returns: total, countries, toolcall_response_at

place_orders_to_suppliersOrder: Place Orders with SupplierA
Destructive
Inspect

[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.

Inputs: status (required), selection_mode (required), sales_channel_id (required), supplier_platform_id (required), +11 more. Returns: url, task_id, task_type, toolcall_response_at

publish_products_to_storesPush: Push Products to StoreA
Destructive
Inspect

[Import List Product] [What it does] Publishes import-list products to selected stores in one call, creating store products whose listing status and buyer visibility follow the chosen settings; up to 100 product-store targets per call. [When to use] Use it only after the user gives final confirmation that the selected products should be published to the named stores. [When not to use] For product content or category changes, use update_pre_publish_product_content or update_pre_publish_product_organization. For existing store-product price or stock changes, use update_managed_store_product. [How to use]

  • When preparing the request, use the current list_stores result to match every target dsers_store_id and inspect its sales_channel_name. Reuse the result already obtained while selecting the target stores; call list_stores only if it has not been called in the current workflow or the target-store information is unavailable or has changed.

  • Treat a target store as Shopify only when the matching sales_channel_name equals Shopify case-insensitively. Never infer the platform from the store name, domain, IDs, prior knowledge, or another store.

  • Every Shopify target store must have exactly one entry in the request's top-level stores[], with a shipping_profile containing both profile_id and location_id. Copy both IDs from the same store and Shipping Profile returned by list_stores.

  • If multiple Shipping Profiles or Locations are available and the user has not specified one, ask the user to choose. Never guess, combine IDs from different profiles, or reuse IDs from another store.

  • Before publishing, suggest that the user review or update Organization and Category settings. If the user chooses to do so, call get_pre_publish_product_organization once per target store with the complete selected import_item_ids; call update_pre_publish_product_organization once per store only for changes the user explicitly chooses. Products with no requested Organization or Category changes require neither call.

  • Before every publish, call get_push_shipping_recommendation for every exact import_item_id x dsers_store_id target in the request.

  • Set items[].stores[].shipping_method_id only to the service_id explicitly selected by the user for that exact product-store target. Otherwise omit it. Never infer, reuse, or obtain it from another target or source.

  • Every item must use the same target-store set. Send the user's complete selected stores in one call; separate product groups that need a different store set. The expanded matrix supports up to 100 product-store targets.

  • Immediately before task creation, the service rereads every product's latest state and performs the full batch preflight, including input consistency, store ownership and status, store platform, local variant/price/cost/stock safety, Product BFF push-before checks, pricing-rule prices, explicit logistics, and Shopify Shipping Profile ownership. Every Shopify target must have a valid Shipping Profile and Location belonging to that exact store. If any target is blocked, no task is created.

  • sales_channels is passed through for every target. Unsupported channels may not take effect but do not block the push.

  • product_status and publish_to_online_store are independent. Omitted options use DSers or store defaults, so show effective values before confirmation.

  • An accepted write returns task_type and task_id; poll get_job_status until terminal. The write is not idempotent and may partially succeed after acceptance, so never automatically resend it when the outcome is unknown. [Side effects] Creates store products in every selected store and may make them buyer-visible immediately. [Confirmation] Required and never skippable. Before calling, show every product-store target, its platform, effective publication settings, and the selected Shopify Shipping Profile and Location.

Inputs: items (required), stores, taxable, image_strategy, +8 more. Returns: message, task_id, task_type, toolcall_response_at

recommend_apps_to_installStore: Recommend AppsA
Read-onlyIdempotent
Inspect

[Plugins] [What it does] Recommends every visible sales-channel or supplier-platform application of the selected type that is not yet installed; read-only. [When to use] Use when the user wants to discover another channel or supplier platform. [When not to use] To install and authorize a selected sales-channel application, use start_store_connection; to inspect connected stores, use list_stores. [How to use] Set app_type to seller, supplier, or all (the default). The Tool does not provide keyword filtering or caller-controlled pagination. An empty recommendation list is valid. [Side effects] Read-only; installs or authorizes nothing. [Confirmation] No confirmation required. [Follow-up] If the user selects a channel application, continue with start_store_connection; otherwise report the recommendations or empty result and stop.

Inputs: app_type. Returns: recommendations, toolcall_response_at

search_ai_mapping_candidatesMyProduct: Find AI Mapping CandidatesA
Read-onlyIdempotent
Inspect

[Store Products] [What it does] Finds visually similar supplier item for one DSers product via image search, with price, stock, freight, rating, and similarity evidence; creates or applies no mapping. [When to use] Use when the merchant wants to compare suppliers before mapping a managed product. [When not to use] For a general supplier-catalog search, use search_supplier_products; to start the selected mapping computation, use start_ai_product_mapping. [How to use] Copy dsers_product_id from list_managed_store_products; ship_to sets destination context for availability and freight. Zero matches is a valid result and may include a reason; missing price, rating, or similarity remain unknown. [Side effects] Read-only; neither creates nor applies a mapping. [Confirmation] No confirmation required. [Follow-up] If the merchant selects a suitable candidate, start its computation with start_ai_product_mapping; if none fits, report the result and stop.

Inputs: dsers_product_id (required), refresh, ship_to. Returns: ship_to, refreshed, candidates, next_actions, +4 more

search_store_productsMyProduct: Search Store ProductsA
Read-onlyIdempotent
Inspect

[Store Products] [What it does] Searches products directly on a seller's store platform (e.g. Shopify), not DSers My Products; used to inspect store products or as an import source. [When to use] Use to find what a store sells or to locate store products for importing into DSers. [When not to use] For products already managed in DSers, use list_managed_store_products; to import selected products, use import_store_products_to_dsers. [How to use] Copy dsers_store_id from list_stores; pages are 1-based; pass the previous next_since_id unchanged as since_id for the next page. Each item's already_imported state is included; an empty result is valid. [Side effects] Read-only; no store or DSers data changes. [Confirmation] No confirmation required. [Follow-up] If importing is the goal and the user selects products not already in DSers, continue with import_store_products_to_dsers; otherwise report the result and stop.

Inputs: dsers_store_id (required), page, keyword, since_id, +1 more. Returns: items, pagination, dsers_store_id, toolcall_response_at

search_supplier_productsSupplier: Search by Keyword or ImageA
Read-onlyIdempotent
Inspect

[Supply Product] [What it does] Searches supplier products by keyword or image across the account's visible supplier platforms, returning comparable candidates and echoing the filters that actually took effect. [When to use] Use it when the merchant wants to find products to sell, compare suppliers, or match an uploaded image; the agent also calls it first to obtain the supplier platform ID and product ID needed before a detail lookup or an import. Trigger words: sourcing, find a supplier, same as this image, best sellers, cost price. [When not to use] For variants, stock or per-country shipping on one known product use get_supplier_product and list_supplier_product_shipping_methods_and_cost; to import or map use create_pre_publish_products; for products already in the merchant's stores use list_managed_store_products. [How to use]

  • Paging depends on scope: cursor paging and a larger page size work only when one supplier platform is selected; an all-platform search returns a fixed slice per platform, so pick a platform before paging.

  • Each candidate may include supplier_product_url; Agent and 1688 Dropshipping candidates use the configured DSers product-detail page because those platforms do not expose a public supplier-site URL.

  • Compare only the metrics marked available on a candidate, and only in the base currency; unmarked metrics are unknown, and original supplier prices carry different currencies, so never infer or mix them.

  • Filters are adapted per platform: trust the echoed effective conditions and tell the merchant which filters did not apply, rather than claiming the results meet every condition.

  • If some platforms fail while others return candidates, treat it as partial coverage — report the gap and continue; do not retry the whole search or answer "nothing found". [Side effects] Read-only; never imports, edits or maps products. [Confirmation] Not required.

Inputs: sort, cursor, keyword, ship_to, +15 more. Returns: candidates, conditions, pagination, toolcall_response_at

send_buyer_tracking_notificationOrder: Send Tracking EmailA
Destructive
Inspect

[Order] [What it does] Asynchronously requests a Shopify fulfillment tracking notification for the buyer of one owned order; Shopify only. [When to use] Use when the merchant wants Shopify to notify the buyer about tracking for fulfilled items that already have tracking information. [When not to use] To fulfill items or synchronize tracking to the seller store, use sync_existing_tracking_numbers_to_store first. This tool does not apply to non-Shopify platforms. [How to use]

  • Copy one exact dsers_order_id from get_order after checking the fulfilled items and tracking information. The request is order-wide and cannot select a subset of line items.

  • A successful response contains only message: it means DSers accepted an asynchronous notification request, not that Shopify sent it or the buyer received it. Shopify may suppress an identical recent update.

  • Send once, never auto-retried. If the outcome is unknown, check the Shopify order and buyer notification history before deciding what to do; get_order can confirm order and tracking prerequisites but cannot confirm notification delivery. [Side effects] May send an external tracking notification to the buyer. [Confirmation] Required, never skippable: show the exact order, eligible fulfilled items, and tracking information, and state that this may contact the buyer. [Follow-up] After acceptance, check the Shopify order and buyer notification history later; if rejected, report the error and stop.

Inputs: dsers_order_id (required). Returns: message, toolcall_response_at

simulate_pricing_ruleMyProduct: Calculate Price by Pricing RuleA
Read-onlyIdempotent
Inspect

[Pricing Rule] [What it does] Simulates the selling price and compare-at price that the store's Pricing Rule would compute for a DSers-managed product's mapped variants in a given destination country and cost, without writing anything back. [When to use] Use when the user wants to preview what price a Pricing Rule would produce before actually applying it, such as after a cost or destination change. [When not to use] To actually write the live price, use update_managed_store_product. To view or edit the rule itself, use get_pricing_rule/update_pricing_rule. [How to use] dsers_product_id and ship_to (2-letter country code) are required. Optionally list specific sales_product_variant_id values with an optional cost override (defaults to the mapped supplier cost); omitting the list simulates all mapped variants. Unmapped variants never appear in the results. [Side effects] None; read-only and never writes back to the product. [Confirmation] Not required.

Inputs: ship_to (required), dsers_product_id (required), sales_product_variant_list. Returns: message, operation, mapping_type, dsers_product_id, +2 more

start_ai_product_mappingMyProduct: Create AI Mapping TaskA
Destructive
Inspect

[Store Products] [What it does] Starts an asynchronous AI Mapping computation between one DSers product and one supplier candidate; it does not apply the resulting mapping. [When to use] Use after the merchant selects a supplier candidate for that product. [When not to use] To find or compare candidates, use search_ai_mapping_candidates; this tool cannot apply a computed mapping — that requires the mapping-apply tool associated with get_store_product_mapping. [How to use] Copy dsers_product_id from list_managed_store_products; copy supplier_platform_id and supplier_product_id from the same search_ai_mapping_candidates candidate. Read task_created and next_step before acting: a newly created task has task_created=true; a false value can point to an existing task, an existing completed result to apply, or an Applied result requiring confirmed remap. Follow the returned status_tool only when present, using its task_type and task_id; do not treat running status as completion. [Side effects] A response with task_created=true consumes 8 AI Credits and creates a computation task; history-only responses create nothing, consume no Credits, and leave the product mapping unchanged. [Confirmation] Requires explicit, non-skippable confirmation; show the exact product, candidate, and 8 AI Credits cost first. [Follow-up] Follow next_step: poll an indicated new or existing task until terminal, apply an indicated completed result only after its separate confirmation, or show the remap preview before calling again with remap=true.

Inputs: dsers_product_id (required), supplier_product_id (required), supplier_platform_id (required), remap, +1 more. Returns: status, country, history, message, +14 more

start_store_connectionStore: Start ConnectionA
Idempotent
Inspect

[Store or Supplier Account] [What it does] Installs one selected application if needed and generates its external authorization link. It supports seller applications for a new store connection and only AliExpress or Alibaba.com for adding a supplier account. A returned link does not mean the store or supplier account is connected. [When to use] Use after the user selects a seller application, or explicitly asks to add an AliExpress or Alibaba.com supplier account. [When not to use] For an existing seller store needing reconnection, use start_store_reauthorization. Other supplier applications cannot add accounts through this Tool. [How to use] Provide exactly one identifier: copy recommend_apps_to_install.recommendations[].app_id into sales_channel_id for a seller application, or into supplier_platform_id only when that recommendation is AliExpress or Alibaba.com. An already-installed seller ID may also come from list_stores.stores[].sales_channel_id; an installed supplier ID may come from list_stores.supplier_apps[].supplier_platform_id. Never send both IDs. country is seller-only and should be passed only when that seller platform requires a country-specific flow. A successful response returns app_type, the matching sales_channel_id or supplier_platform_id, app_name, a validated HTTPS authorization_url, and generated_at; external authorization is still pending. The upstream platform controls URL lifetime and reuse. If the outcome is unresolved, verify seller connections or supplier accounts in DSers before retrying. [Side effects] May install the selected seller, AliExpress, or Alibaba.com application. [Confirmation] Requires explicit, non-skippable confirmation; show the selected application and country choice first. [Follow-up] Give the returned authorization_url to the user to complete authorization on the platform, then verify the new connection in DSers.

Inputs: country, sales_channel_id, supplier_platform_id. Returns: app_name, app_type, generated_at, sales_channel_id, +3 more

start_store_reauthorizationStore: Reauthorize ConnectionAInspect

[Store] [What it does] Requests a platform reauthorization link for an owned store; generating the link does not mean reauthorization is complete. [When to use] Use for a store with a connection error, expired authorization, or another reconnection need. [When not to use] For a brand-new store connection, use start_store_connection; this tool is only for reauthorizing an existing store. [How to use] Copy dsers_store_id from list_stores after checking current status. A successful response returns dsers_store_id, sales_store_name, sales_channel_id, a validated HTTPS authorization_url, and generated_at; this means only that the link was generated. The upstream platform controls its lifetime and reuse policy. If the outcome is unresolved, verify with list_stores before retrying. [Side effects] Generating the link does not change authorization status. [Confirmation] Requires user confirmation before generating the link; skippable per authorization policy. [Follow-up] Give the returned authorization_url to the user to complete platform authorization, then verify the connection with list_stores.

Inputs: dsers_store_id (required). Returns: generated_at, dsers_store_id, sales_channel_id, sales_store_name, +2 more

sync_existing_tracking_numbers_to_storeTracking: Sync Existing Numbers to StoreA
Destructive
Inspect

[Tracking Number / Fulfillment] [What it does] Synchronizes the tracking numbers already stored on one DSers order to the sales channel. After synchronization, the sales channel may automatically update the order's shipment or fulfillment status. [When to use] Use after the supplier has shipped and the DSers order already contains the correct tracking numbers that need to be synchronized to the store. [When not to use] This Tool does not accept new tracking numbers or support selecting specific items. To provide new tracking numbers for selected sales-side items, use update_tracking_numbers_to_store. Use get_package_details to inspect tracking events. Before calling this Tool, use get_order to review the order items and existing tracking numbers. [How to use]

  • Copy dsers_order_id from get_order. Order ownership and currently eligible items are validated before synchronization.

  • Keep switch_fulfillment_service=false for the normal synchronization path.

  • switch_fulfillment_service is supported only for Shopify orders. Set it to true only when normal synchronization fails because the Shopify items are assigned to another fulfillment service and the response explicitly instructs you to switch.

  • Switching the fulfillment service may assign the affected Shopify items to the DSers fulfillment location and affect future orders for those items. Non-Shopify orders must keep this value false.

  • A successful response means only that the synchronization request was accepted. It does not confirm that the sales channel has completed the tracking-number update or fulfillment.

  • This operation is not idempotent. If the outcome is unclear, refresh get_order and the sales-channel order instead of retrying automatically. [Side effects] May update the tracking numbers, shipment status, and fulfillment status of the sales-channel order. The Shopify switch path may also change the fulfillment location assigned to the affected items. [Confirmation] Always required. Before calling this Tool, show and confirm the exact store, order, currently eligible items, existing tracking numbers, selected synchronization path, and any possible Shopify fulfillment-location changes.

Inputs: dsers_order_id (required), switch_fulfillment_service. Returns: message, toolcall_response_at

sync_supply_order_tracking_numberTracking: Refresh TrackingAInspect

[Tracking / Logistics] [What it does] Requests an asynchronous refresh of carrier tracking status for one tracking number and syncs it into DSers; does not return refreshed events immediately. [When to use] Use when a shipment's tracking looks stale and fresh data is needed before reporting progress. [When not to use] For current tracking events, use get_package_details; to find a tracking number, use list_packages. [How to use] Supply one tracking number tn copied from list_packages. accepted only means the request was accepted, not completed, and does not show that stored status changed — there is no completion flag or refreshed events in the response. Dispatch once, never auto-retry; check get_package_details first if the outcome is unclear. [Side effects] May update stored tracking data. [Confirmation] Required; skippable per authorization policy. [Follow-up] If refreshed status is still needed, wait and check get_package_details; if rejected, report the message and stop.

Inputs: tn (required). Returns: accepted, toolcall_response_at

update_managed_store_productMyProduct: Update Price or StockA
Destructive
Inspect

[Store Products] [What it does] Changes selling price, cost, compare-at price, currency, or stock for exact variants of one DSers-managed store product, and handles the matching auto-sync switches. [When to use] Use it when the user asks to change an existing product's price, cost, or stock, and when the agent has already resolved the exact variants and target values. Trigger words: change the store price, reprice a live product, update stock, update cost. [When not to use] To inspect current prices, stock, or variants, use get_managed_store_product. For a product not yet pushed to a store — an item still on the DSers Import List — use update_pre_publish_product_price. To change or apply a store Pricing Rule in bulk, use the pricing-rule or bulk-price Tool. It edits one product only and cannot bulk-reprice by filter. [How to use]

  • Resolve IDs in order: dsers_store_id from list_stores, dsers_product_id from list_managed_store_products items[].dsers_product_id, and sales_product_variant_id from get_managed_store_product sales_product_variant_list[].sales_product_variant_id. SKUs, option text, and supplier variant IDs are rejected.

  • Every price_updates item requires sales_product_variant_price_amount, so resend the current selling price even when only sales_product_variant_cost_amount, sales_product_variant_compare_at_price_amount, or currency changes.

  • Amounts are major-unit decimal strings ("19.99", never "1999"), and currency sets the allowed precision; omit it only when the variant or product already has one.

  • sales_product_variant_inventory_quantity replaces the current quantity and is never a delta.

  • price_auto_sync_action is mandatory with price updates and stock_auto_sync_action with stock updates; disable permanently turns that sync off.

  • This write is not idempotent. Send it once, for at most 100 variants of a single product.

  • Compare price_variants_updated and stock_variants_updated with what you requested; if they differ or the outcome is unknown, re-read with get_managed_store_product instead of retrying. Subscription errors block the write and are returned as structured errors.

  • This tool covers only products already pushed to a store, including Draft status; for items not published yet, use update_pre_publish_product_price. If the publish state is unclear, or the product exists on both sides, ask before changing the live price. [Side effects] Changes buyer-visible prices and stock; disable also switches off auto-sync. [Confirmation] Required: show store, product, variants, and final values first.

Inputs: dsers_store_id (required), dsers_product_id (required), price_updates, stock_updates, +2 more. Returns: auto_sync_results, toolcall_response_at, price_variants_updated, stock_variants…

update_order_informationOrder: Update DetailsA
Destructive
Inspect

[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.

Inputs: dsers_order_id (required), address, freight, supplier_platform_id, +4 more. Returns: message, toolcall_response_at

update_order_supplierOrder: Edit SupplierA
Destructive
Inspect

[Order] [What it does] Changes the supplier product and/or fulfillment Variant used by one order item. It can switch suppliers, select another product or Variant from the same supplier, or change only the fulfillment Variant while keeping the supplier and product unchanged. This edit affects the current order only: it does not change the buyer's original sales-channel SKU/Variant or the product's long-term Mapping. [When to use] Use when the current supplier product or Variant is unavailable, out of stock, mispriced, cannot ship, or when the user explicitly chooses a different fulfillment Variant for this order. [When not to use] To change the permanent product Mapping used by future orders, use apply_product_mapping. To change the buyer-facing sales-channel SKU/Variant, use the sales-channel workflow. The current supplier row must still be unplaced, cancelled, or failed; placed, in-progress, paid, shipped, fulfilled, or otherwise locked rows cannot be edited. [How to use] Read the exact order and item with get_order, including its current supplier row and fulfillment Variant. Resolve and validate the selected supplier product, fulfillment Variant, stock, price, destination support, and freight. Pass exactly one of supplier_product_id and supplier_product_url; supplier_platform_id is required with either input. Before writing, show the old and new supplier, supplier product, fulfillment Variant name and ID, product price, freight, stock, and net cost change; label unavailable comparison values as unavailable rather than guessing. Obtain the user's explicit confirmation and their explicit allow_future_mapping_override choice. true allows a later product-level Mapping update to replace this order's manual fulfillment selection; false keeps the manual selection fixed against later Mapping updates. This choice does not modify the buyer's original SKU/Variant or immediately change product-level Mapping. If the write outcome is unknown, re-read get_order and the Orders page; never automatically retry. [Side effects] Changes the supplier product, fulfillment Variant, and applicable freight used for this order item, which can change fulfillment cost and delivery details. It does not change the buyer's original sales-channel SKU/Variant or immediately modify product-level Mapping. [Confirmation] Required, never skippable: show the complete old-versus-new fulfillment comparison and obtain the Mapping-override choice before calling.

Inputs: dsers_order_id (required), dsers_order_item_id (required), supplier_platform_id (required), allow_future_mapping_override… Returns: message, toolcall_response_at

update_pre_publish_product_contentImport: Update Product ContentA
Destructive
Inspect

[Import List Product] [What it does] Changes non-price content of one pre-publish product — an item on the DSers Import List page: title, description, images, package, options and option values, variants, SKUs, and stock, including deletions and duplications. [When to use] Use it when the user wants to edit, clean up, or save translated content for a pre-publish product, and once the agent has final wording or has identified the exact rows to change. Trigger words: change the title, edit description, remove images, delete variants, fix this import list product, save translation. [When not to use] For selling or compare-at prices, use update_pre_publish_product_price. For a product already pushed to a store, including Draft status, use update_managed_store_product. It does not translate; it only saves content you already produced. [How to use]

  • Take import_item_id and resource_version from a fresh get_pre_publish_product; stale versions are rejected, and at least one editable field must be sent.

  • Every option, option-value, and variant operation needs the ID plus its zero-based index, because duplicated rows keep the original ID.

  • supplier_product_image_url_list replaces the whole list rather than appending; resend all images even to add one, the first becomes the main image, and each must be a public HTTPS URL with a resource path.

  • Deletions cascade: removing an option value deletes every variant using it, and delete_options keeps only variants matching the reserve value you name. At least one option, one value, and one variant must remain.

  • Titles of variants that have options are derived; rename them through rename_option_values, not supplier_product_variant_list[].supplier_product_variant_name.

  • An empty string clears a field while omitting it preserves the field; cost, currency, and supplier are protected and cannot be changed.

  • This write is not idempotent. Send it once. The server verifies the stored content before returning import_item_id, changed_fields, changed_variant_ids, and changed_option_ids; it does not return a new resource_version. Before another write, or if the outcome is unknown, re-read with get_pre_publish_product instead of resending.

  • Import List products, draft products, and pre-publish products name the same objects; accept the old wording and answer in generic product terms rather than sending the user to a page. [Side effects] Rewrites the pre-publish product; deletions cannot be undone. [Confirmation] Required but skippable; always confirm deletions first.

Inputs: import_item_id (required), resource_version (required), package, delete_options, +10 more. Returns: changed_fields, import_item_id, changed_option_ids, changed_variant_ids, +1 more

update_pre_publish_product_organizationImport: Update Organization & CategoryAInspect

[Import List Product] [What it does] Saves actual Organization, Category, or URL handle changes for one to 100 pre-publish products in one store. [When to use] Use it after get_pre_publish_product_organization has returned the current selections and available Organization and Category choices for the same store so they can be reviewed with the user, and only after the user has chosen concrete listing changes. If the user keeps all current settings, skip this Tool. [When not to use] To read available choices, use get_pre_publish_product_organization. To publish, use publish_products_to_stores. Product content and prices are out of scope. [How to use]

  • Send all selected products in items. Every item requires import_item_id and at least one actual update field: category_ids, organizations, or url_handle.

  • Omitted fields are preserved. Empty category_ids or organizations clears that setting; an empty url_handle clears the handle.

  • Use only field names and value IDs returned for the same store. create_values creates store-level values that may persist if a later product assignment fails.

  • The service serializes writes to the same user and import item, rereads the latest item while holding that lock, applies only supplied fields, and performs read-after-write confirmation.

  • Batches may partially succeed. A successful item returns its IDs and optional created_values; a failed item returns failure_code, failure_reason, failure_hint, and retryable. [Side effects] Changes product store settings and may create store-level Organization values. [Confirmation] Required but skippable; use only values the user explicitly chose.

Inputs: items (required), dsers_store_id (required). Returns: items, failed, warnings, created_values, +3 more

update_pre_publish_product_priceImport: Update Product PricesA
Destructive
Inspect

[Import List Product] [What it does] Supports three modes for one pre-publish product on the DSers Import List: variants changes selling and compare-at prices for exact variant rows, fixed_price sets one selling price for every variant, and pricing_rule only opens or closes the item's item-level pricing rule. Every successful price change automatically closes the item's item-level pricing rule in the same write. It never changes the store-level Pricing Rule. [When to use] Use it when the user wants to reprice a pre-publish product or explicitly open or close that import item's pricing rule. Before a price change, re-read the item, compute every target price, disclose that the item-level pricing rule will be closed, and proceed only after the agent has obtained confirmation. Trigger words: reprice a product that is not published yet, adjust prices before publishing, set one price for every variant, open or close this import item's pricing rule. [When not to use] For titles, images, options, or other non-price content, use update_pre_publish_product_content. For a product already pushed to a store, including Draft status, use update_managed_store_product; this tool never syncs store prices. To change the store-level Pricing Rule itself, use update_pricing_rule. [How to use]

  • Take import_item_id and resource_version from a fresh get_pre_publish_product; a version more than a few minutes old is rejected as stale.

  • Amounts are plain decimals with up to two places and are always stored as 77.77 to 7777; the dsers_store_id currency is a display label only and changes neither conversion nor precision.

  • Pick exactly one mode and send only its matching argument: variants with supplier_product_variant_list, fixed_price with fixed_price, or pricing_rule with pricing_rule_status.

  • variants and fixed_price automatically close the item-level pricing rule. Do not send pricing_rule_status with either price mode. Price changes and the close happen atomically in one Product BFF write and are both verified by read-after-write.

  • pricing_rule changes only the item-level pricing-rule status. It does not change prices, compare-at prices, price bounds, or is_price_edited; do not send price fields in this mode.

  • fixed_price applies atomically to every variant and cannot target a subset.

  • supplier_product_variant_list accepts 1 to 100 rows in variants mode; add variant_index whenever a supplier_product_variant_id is duplicated.

  • Send supplier_product_variant_compare_at_price_amount only on explicit request: a non-empty value must not be below the resulting price, and an empty string clears it. Never raise or clear it on your own when only price was requested.

  • This write is not idempotent. Send it once. The server verifies the stored update before returning import_item_id, changed_fields, and message; it does not return a new resource_version or warning list. Before another write, or if the outcome is unknown, re-read with get_pre_publish_product to confirm prices, compare-at values, the item-level rule, and the latest version instead of resending.

  • Stock or cost requests must go to update_managed_store_product; this tool changes only selling and compare-at prices. When the publish state is unclear, or the same product exists both as a pre-publish item and a store product, ask which side to change instead of defaulting.

  • Import List products, draft products, and pre-publish products name the same objects; accept the old wording and answer in generic product terms rather than sending the user to a page. [Side effects] variants and fixed_price persist pre-publish prices and close the item-level pricing rule; pricing_rule changes only that status. Published store products are unaffected. [Confirmation] Required, never skippable. For price modes, show before and after prices per variant and state that the item-level pricing rule will close. For pricing_rule, show only the requested status change.

Inputs: mode (required), dsers_store_id (required), import_item_id (required), resource_version (required), +3 more. Returns: message, changed_fields, import_item_id, toolcall_response_at

update_pricing_rulePricing: Update Store RuleAInspect

[Pricing Rule] [What it does] Saves one owned store's Pricing Settings. A call may update any combination of the store-wide Basic or Advanced fixed rule, price endings, and exchange-rate mode. Supported rule modes are none, basic, and advanced; Advanced custom formulas are view-only and cannot be modified with this Tool. [When to use] Use only when the user explicitly asks to change a store's Pricing Settings, after a fresh get_pricing_rule read and after the user confirms the exact resulting store-wide configuration. [When not to use] To inspect settings, including an Advanced custom formula, use get_pricing_rule. To preview a product price, use simulate_pricing_rule. To change live or pre-publish product prices, use the applicable product update Tool. This Tool changes the rule itself; it does not reprice existing products. [How to use]

  • Always call get_pricing_rule first. Copy dsers_store_id and resource_version unchanged. A successful write invalidates that version.

  • For a rule update, choose exactly one mode and its matching complete body: mode=none sends no rule body; mode=basic requires basic_rule; mode=advanced requires advanced_rule with formula_mode=fixed. Never send a body belonging to another mode.

  • Advanced formula_mode=fixed requires fixed_ranges and fixed_rest and must not send custom fields. Advanced formula_mode=custom, custom_ranges, and custom_rest are read-only and must not be submitted. Inactive saved Advanced fields are preserved.

  • Basic and Advanced fixed boundaries are inclusive USD costs with at most two decimal places and min < max. Their bounded gaps are completed on the 0.01 grid from the matching rest formula. Collections may contain at most 100 ranges after completion.

  • Advanced mode requires the current plan's pricing-rule benefit; unsupported plans receive an upgrade-required error before any write.

  • The rule, cents, and currency sections are updated independently. Omit top-level mode for a cents-only or currency-only update. Omitted sections are preserved; only an explicit false disables a cent-ending switch. A custom rate requires custom mode: mode=default omits exchange_rate; mode=custom requires a positive exchange_rate.

  • This Tool is not idempotent. Send once. If the result is unknown or partial, call get_pricing_rule and submit only what still differs. On success the server has read back and verified the saved state and returns the new resource_version. [Side effects] Changes store-wide Pricing Settings used by future price calculations, but does not directly rewrite existing product prices. [Confirmation] Mandatory and not skippable. Show the store, resulting active mode and formula, completed ranges, and every cents or currency change before calling.

Inputs: dsers_store_id (required), resource_version (required), mode, cents, +3 more. Returns: resource_version, toolcall_response_at

update_store_product_price_in_bulkMyProduct: Create Manual Store Price Update TaskA
Destructive
Inspect

[Store Products] [What it does] Starts a whole-store price-sync task for one to 20 owned stores. Product BFF applies each store's currently enabled Pricing Rule to all eligible mapped products. [When to use] Use when the merchant explicitly wants to reapply the enabled Pricing Rule across complete stores. [When not to use] For one exact product or variant, use update_managed_store_product. For pre-publish products, use update_pre_publish_product_price. This Tool does not accept product filters, variant filters, fixed/percentage adjustment inputs, or Pricing Rule changes. [How to use] Copy the complete dsers_store_ids selection from list_stores. The preflight verifies store ownership, an enabled Pricing Rule, and no conflicting active task; it does not calculate a per-product price preview. The write creates an async task; after confirmation, poll get_job_status with the returned task_type and task_id; its result contains the current and final per-store progress. If task creation is uncertain, check status instead of creating another task. [Side effects] May change buyer-visible prices for every eligible mapped product in each selected store. [Confirmation] Required, never skippable: show the exact stores and explain that their enabled Pricing Rules apply store-wide.

Inputs: dsers_store_ids (required). Returns: status, task_id, task_type, toolcall_response_at

update_supplier_orderOrder: Refresh Supplier DetailsAInspect

[Order] [What it does] Starts an asynchronous refresh of supplier order details for one store or all owned stores; does not return refreshed data immediately. [When to use] Use when supplier order details (such as tracking or status) look stale or missing and must be refreshed before rereading the order; commonly the final write-back step in flows like Order Address Fix. [When not to use] For reading existing data without a refresh, use get_order or list_orders; to change order content itself, use the order-update tool, not this one. [How to use] Copy dsers_store_id from list_stores; omitting it covers all owned stores, so confirm scope first. A successful response returns task_type and task_id; use both with get_job_status until terminal=true. The response means only that the asynchronous job was created, not that supplier details are already refreshed. Dispatch once; if the outcome is unknown, poll the returned task instead of resubmitting. [Side effects] Creates a synchronization job that may update stored supplier details. [Confirmation] Requires non-skippable user confirmation; show the exact store scope first. [Follow-up] After the task reaches a successful terminal state, verify updated supplier details with get_order or list_orders; if it fails, report the task status and message, then stop.

Inputs: dsers_store_id. Returns: task_id, task_type, toolcall_response_at

update_tracking_numbers_to_storeTracking: Update Numbers to StoreA
Destructive
Inspect

[Tracking Number / Fulfillment] [What it does] Adds or updates tracking numbers for selected sales-side order items. Each item supports one or more tracking numbers, which are sent directly to the sales channel. If an item already has tracking numbers, the complete list submitted in this request replaces the existing list. Appending is not supported. [When to use] Use when you need to set new tracking numbers for selected sales-side items in one DSers order or replace their existing tracking numbers. [When not to use] To synchronize tracking numbers already stored on the DSers order, use sync_existing_tracking_numbers_to_store. This Tool cannot append new tracking numbers to the existing list. Use get_package_details to inspect tracking events. Before calling this Tool, use get_order to review the order, sales-side items, and existing tracking numbers. [How to use]

  • Copy dsers_order_id from get_order.

  • Copy each dsers_order_item_id from the order's items[].dsers_order_item_id. Do not use supplier_order_item_id.

  • tracking_updates must be a non-empty array. Each update may target only one sales-side item.

  • Each update's tracking_numbers must be a non-empty array containing one or more tracking numbers.

  • The complete tracking_numbers list in each update replaces the existing tracking numbers of the corresponding item.

  • The same dsers_order_item_id must not appear more than once in tracking_updates.

  • Tracking numbers are trimmed and deduplicated. Empty tracking numbers are rejected.

  • Order ownership and item membership are validated before the update is sent.

  • A successful response means only that the sales channel accepted the update request. It does not confirm that the final state has been updated.

  • This operation is not idempotent. If the outcome is unclear, refresh get_order and the sales-channel order instead of retrying automatically. [Side effects] Replaces the existing tracking numbers of the selected sales-side items and may change their shipment or fulfillment status. [Confirmation] Always required. Before calling this Tool, show and confirm the exact store, order, sales-side items, new tracking numbers for each item, existing tracking numbers that will be replaced, and any possible shipment or fulfillment-status changes.

Inputs: dsers_order_id (required), tracking_updates (required). Returns: message, toolcall_response_at

validate_order_addressOrder: Validate AddressA
Read-onlyIdempotent
Inspect

[Order] [What it does] Read-only check of one order's currently saved shipping address against DSers required-field, length, and format rules; never accepts or saves candidate address fields. [When to use] Use to inspect the saved address or investigate a reported address-rule failure before deciding whether an update is needed. [When not to use] It cannot validate an unsaved candidate address or confirm real postal deliverability. To change the address, use update_order_information. [How to use] Copy dsers_order_id from list_orders or get_order. Optional supplier_platform_id selects which supplier's address rules to load; omit, empty, or 0 defaults to AliExpress 159831080. address returns the currently saved shipping address and recipient details using the same fields and values as get_order.order.address, including street address lines, name, phone, email, tax ID, passport numbers, company, and birthday when populated. sales_order_recipient_birthday is returned exactly as stored; AliExpress Brazil rules use DDMMYYYY. Values are returned as stored, without masking; empty fields are omitted. Only supported required, length, and regexp validators with an executable pattern are included; fields and rule types this tool does not apply are omitted. passed_fields lists fields whose effective validators have no failed or unevaluable result. error_fields contains definite validation failures and returns every effective validator applied by this tool to each affected field; inspect those validator statuses because the same field may also contain an unevaluable rule. unevaluated_fields contains fields with no definite failure whose effective validators could not be checked safely. Empty error_fields and unevaluated_fields mean only that the effective rules detected no problem; they do not confirm postal deliverability. [Side effects] Read-only; no order data changes. [Confirmation] No confirmation required. [Follow-up] If error_fields is non-empty, collect the corrected fields, show the proposed change, and call update_order_information after confirmation. If unevaluated_fields is non-empty, report that an effective validator could not be checked safely. Call this Tool again only after the update if the saved address must be checked again.

Inputs: dsers_order_id (required), supplier_platform_id. Returns: address, error_fields, passed_fields, dsers_order_id, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Automate AliExpress/Alibaba/Accio dropshipping product import to Shopify & Wix via DSers. 13 tools + 4 prompts for bulk import, pricing rules, SEO optimization, pre-push safety checks, multi-store push, variant editing, product management, and automated supplier replacement with SKU-level variant matching. Zero-password browser login. v1.5.7.
      13
      59 npm
      26
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and developers to search AliExpress products, compare prices and exact order counts, inspect variants and seller details, check shipping costs and delivery times by country, and read buyer reviews.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that automates importing products from AliExpress, Alibaba, and Accio into DSers and pushing them to Shopify or Wix stores, with features like bulk import, pricing rules, and title cleanup.
      9
      59 npm
      4
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.