DSers MCP product

Retrieve available stores, supported rule families (pricing, content, images), push options, and visibility modes for the connected DSers account. Call this first before any other tool — the response contains store IDs, shipping profiles, and configuration constraints needed by all subsequent operations. Returns: provider_label, source_support (aliexpress/alibaba/1688), stores (each with store_ref, display_name, platform, shipping_profiles), rule_families, push_options, notes.

Check and normalize a rules object against the provider's capabilities before importing. Use this to verify pricing, content, and image rules are valid and see exactly which ones will be applied. Returns: effective_rules_snapshot (what will actually be applied), warnings (adjustments made), errors (blocking issues that must be fixed before calling dsers.product.import).

Import product(s) from supplier URL(s) into the DSers import list and return a preview bundle with title, prices, images, and variants. Single mode: provide source_url. Batch mode: provide source_urls_json with an array of URLs or objects. Each successful import returns a job_id needed for dsers.product.preview, dsers.product.visibility, and dsers.store.push. Returns: job_id, status, title_before/after, price_range_before/after, images_before/after, variant_count, variant_preview (first 5), warnings.

Reload the preview for a previously prepared import job without re-importing. Use this to re-examine title, prices, images, variants, and applied rules for a job created by dsers.product.import. Returns the same structure as dsers.product.import: job_id, status, title, price ranges, images, variants, rules, warnings.

Change the visibility mode of a prepared job before pushing it to the store. Call this between dsers.product.import and dsers.store.push to switch between draft and published. Returns: job_id, status, visibility_mode.

Push one or more prepared import drafts to the connected Shopify or Wix store(s). Three modes: (1) Single push — provide job_id + target_store. (2) Batch push — provide job_ids_json with an array of job IDs or objects; takes priority over job_id. (3) Multi-store push — provide job_id + target_stores_json to push one product to multiple stores. Returns per-job results: job_id, status, target_store, visibility_applied, push_options_applied, job_summary, warnings.

Check the current status of an import or push job. Status lifecycle: preview_ready (after prepare) -> push_requested (after confirm) -> completed or failed. Call this to monitor push progress or verify a job's state before further action. Returns: job_id, status, created_at, updated_at, target_store, visibility_mode, warnings, has_push_result.