dsers_product_delete - Dropshipping MCP Dsers

Delete Product from Import List

dsers_product_delete

Destructive

Permanently delete products from your DSers import list with required confirmation. Removes supplier mappings from the pre-push staging area without affecting live Shopify or Wix store listings.

Instructions

Permanently delete a product from the DSers import list. IRREVERSIBLE — the product cannot be recovered after deletion. Requires explicit confirmation (confirm=true) to execute. If called without confirm=true, returns a confirmation prompt — show this to the user. SCOPE: Only removes the product from DSers import list (pre-push staging area). Products already pushed to Shopify/Wix stores are NOT affected — to remove a store listing, use the Shopify/Wix admin directly. BUSINESS CONTEXT: Deleting from import list means losing the supplier mapping (link between the store product and the AliExpress/Alibaba supplier). If the user wants to re-import later, they will need the original supplier URL. AGENT PROTOCOL: Before calling with confirm=true, always: 1) Show the user the product title and supplier URL. 2) Warn that this cannot be undone. 3) Get explicit user consent (e.g. 'yes, delete it'). Never set confirm=true without the user's explicit approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`import_item_id`	Yes	The import list item ID to delete. Obtain from dsers_product_preview (provider_state.import_item_id) or from searchImportList results.
`confirm`	No	Set to true to confirm deletion. First call without this to get a confirmation prompt, then call again with confirm=true after user approves.

Tool Description Quality Score

S4.9/5.0

Behavior5/5

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

While annotations mark this as destructive, the description adds critical behavioral details: irreversibility warning, the specific two-phase confirmation protocol (returns prompt without confirm=true), business impact (loss of supplier mapping), and exact scope boundaries. No contradictions with annotations.

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?

Excellent structure with clear section headers (IRREVERSIBLE, SCOPE, BUSINESS CONTEXT, AGENT PROTOCOL). Every sentence serves a purpose—warning of permanence, clarifying scope limitations, explaining business consequences, or prescribing agent workflow. Despite length, no waste.

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

Completeness5/5

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

For a destructive, irreversible operation with a two-phase confirmation flow, the description is comprehensive. It covers the action, limitations, side effects, recovery implications, and required agent behavior. No output schema exists, but the description adequately explains the confirmation prompt response behavior.

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, the baseline is 3. The description adds value beyond the schema by specifying the agent protocol for handling confirm (show product title, get explicit user consent) and emphasizing that the confirmation prompt must be shown to the user. Could explain import_item_id acquisition more prominently.

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

Purpose5/5

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

The description explicitly states the specific action (permanently delete), resource (product from DSers import list), and scope limitations (import list only, not Shopify/Wix stores). It clearly distinguishes from sibling tools like dsers_store_push by specifying this only affects the pre-push staging area.

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

Usage Guidelines5/5

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

Provides explicit when-not-to-use guidance ('Products already pushed to Shopify/Wix stores are NOT affected') and directs to alternatives ('use the Shopify/Wix admin directly'). Also clearly documents the two-phase confirmation flow required before execution.

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

Install Server

Dropshipping MCP Dsers

Delete Product from Import List

Instructions

Input Schema

Tool Description Quality Score

Other Tools

Latest Blog Posts

MCP directory API