Skip to main content
Glama

AliExpress / Alibaba / Accio Product Import

dsers_product_import

Import products from AliExpress, Alibaba, or Accio URLs into DSers to preview variants and pricing. Apply pricing rules, customize content, and configure inventory settings during single or batch import operations.

Instructions

Import product(s) from supplier URL(s) into the DSers import list and return a preview. Supports AliExpress, Alibaba, and Accio.com URLs. Provide source_url (single) or source_urls_json (batch). Optionally apply rules at import time via rules_json or flat params. EXPIRED/LOST JOB_ID: Re-import with source_url — DSers finds the existing draft (no duplicate). To UPDATE rules on an existing import, use dsers_product_update_rules instead. SINGLE RESPONSE: compact preview with all variants [name, sell, qty], price_summary, active_rules. BATCH RESPONSE: summary mode (default) returns job_id + key metadata per product (~100 tokens each). Use batch_detail='full' for complete previews. Use dsers_product_preview for individual details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_urlNoSingle supplier product URL. Supports AliExpress (aliexpress.com/item/xxx.html), Alibaba (alibaba.com/product-detail/xxx.html), and Accio.com product links (accio.com/c/...?productId=xxx&ds=aliexpress.com).
source_urls_jsonNoBatch import: JSON array of URL strings or objects with {url, rules?, source_hint?, country?, target_store?, visibility_mode?}. Example: ["https://aliexpress.com/item/123.html", {"url": "https://aliexpress.com/item/456.html", "rules": {"pricing": {"mode": "multiplier", "multiplier": 3}}}]
source_hintNoSupplier platform hint. Valid values: auto, aliexpress, alibaba, accio. Default: auto (detected from URL).auto
countryNoTarget country code for shipping and pricing lookup. Examples: US, GB, DE, FR, AU.US
target_storeNoStore ID or display name from dsers_store_discover. Required when the account has multiple stores.
visibility_modeNoProduct visibility after push. backend_only (default): saved as draft, not visible to shoppers — SAFE, no financial risk. sell_immediately: published and LIVE on the storefront — RISK: verify pricing and inventory first.
job_idNo(DEPRECATED — use dsers_product_update_rules) When provided without source_url, forwards to dsers_product_update_rules internally.
rules_jsonNoRules as JSON string. Keys: pricing, content, images, variant_overrides, option_edits. PRICING: {mode:'fixed_price',fixed_price:9.99} | {mode:'multiplier',multiplier:2} | {mode:'fixed_markup',fixed_markup:5}. VARIANT_OVERRIDES: [{match:'Red',sell_price:9.99,compare_at_price:19.99}]. CONTENT: {title_override, title_prefix, title_suffix, description_override_html, tags_add:['tag']}. Content fields merge individually — set title_prefix without losing description. Clear with '' or null. IMAGES: {drop_indexes, reorder, add_urls, keep_first_n}. OPTION_EDITS (always full replacement): [{action:'rename_option',option_name:'Color',new_name:'Style'},{action:'rename_value',option_name:'Color',value_name:'Red',new_name:'Crimson'},{action:'remove_value',option_name:'Color',value_name:'Gray'},{action:'remove_option',option_name:'Size'}]. Only include families you want to change. Others are preserved automatically.
pricing_modeNoFlat param: pricing mode. Use instead of rules_json for simple pricing.
pricing_multiplierNoFlat param: multiplier value when pricing_mode='multiplier'.
pricing_fixed_markupNoFlat param: markup in dollars when pricing_mode='fixed_markup'.
pricing_fixed_priceNoFlat param: exact price in dollars when pricing_mode='fixed_price'.
title_overrideNoFlat param: replace entire product title.
title_prefixNoFlat param: prepend to product title.
title_suffixNoFlat param: append to product title.
description_override_htmlNoFlat param: replace full description (HTML).
description_append_htmlNoFlat param: append HTML to description.
batch_detailNoBatch response detail level. summary (default): job_id + title + sell_price + cost + variants_count + stock per product (~100 tokens each). full: complete preview per product (can be very large for 10+ products). Single imports always return full preview.
Behavior4/5

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

Beyond annotations (mutation, non-destructive), description adds critical behavioral context: draft/import list workflow, automatic deduplication for re-imports, deprecation of job_id parameter, and response size expectations (~100 tokens per product in summary mode).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information-dense but highly structured with capitalized section headers (EXPIRED/LOST JOB_ID, SINGLE RESPONSE, BATCH RESPONSE). Every sentence conveys distinct operational guidance; no filler despite covering 18 parameters and multiple modes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Extremely complete for a complex 18-parameter tool. Compensates for missing output schema by detailing response formats (compact preview vs summary vs full), covers edge cases (expired job_id, multi-store prerequisites), and explains all enum behaviors.

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

Parameters4/5

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

With 100% schema coverage (baseline 3), description adds value by explaining the mutually exclusive parameter patterns ('source_url (single) or source_urls_json (batch)'), the dual rules approach ('rules_json or flat params'), and conceptual groupings that clarify when to use which parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with specific verb+resource ('Import product(s) from supplier URL(s) into the DSers import list'), explicitly lists supported platforms (AliExpress, Alibaba, Accio), and distinguishes from siblings (dsers_product_update_rules, dsers_product_preview).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when-not-to-use alternatives ('To UPDATE rules on an existing import, use dsers_product_update_rules instead'), explains deduplication behavior for expired jobs, and warns about visibility_mode risks ('RISK: verify pricing and inventory first').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lofder/dsers-mcp-product'

If you have feedback or need assistance with the MCP directory API, please join our Discord server