dsers_product_update_rules - Dropshipping MCP Dsers

Update Rules on Imported Product

dsers_product_update_rules

Update pricing rules, product content, images, and variant configurations on imported dropshipping items. Modify option names, remove values, and adjust markup for Shopify or Wix stores.

Instructions

Update pricing, content, images, or variant rules on an already-imported product. Rules are merged incrementally: pricing/images/variant_overrides replace by family; content merges by field (set title_prefix without losing description). To clear a content field, send it as empty string or null (e.g. title_prefix:''). To remove an entire family, pass null (e.g. rules_json='{"pricing":null}'). option_edits are always fully replaced (ordered operations, not mergeable). OPTION_EDITS actions: rename_option {action,option_name,new_name} — rename e.g. Color→Style. rename_value {action,option_name,value_name,new_name} — rename a value within an option. remove_value {action,option_name,value_name} — remove value and DELETE all variants with that value. remove_option {action,option_name} — remove entire option dimension. RESPONSE: compact preview with active_rules showing all currently applied rules.

Input Schema

TableJSON Schema

Name	Required	Description
`job_id`	Yes	Job ID from a previous dsers_product_import call.
`rules_json`	No	Rules 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_mode`	No	Flat param: pricing mode. Use instead of rules_json for simple pricing.
`pricing_multiplier`	No	Flat param: multiplier value when pricing_mode='multiplier'.
`pricing_fixed_markup`	No	Flat param: markup in dollars when pricing_mode='fixed_markup'.
`pricing_fixed_price`	No	Flat param: exact price in dollars when pricing_mode='fixed_price'.
`title_override`	No	Flat param: replace entire product title.
`title_prefix`	No	Flat param: prepend to product title.
`title_suffix`	No	Flat param: append to product title.
`description_override_html`	No	Flat param: replace full description (HTML).
`description_append_html`	No	Flat param: append HTML to description.
`target_store`	No	Store ID or name from dsers_store_discover.
`visibility_mode`	No	backend_only (default, safe) or sell_immediately (live — confirm with user).

Tool Description Quality Score

S4.6/5.0

Behavior5/5

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

Exceeds annotations by detailing critical merge semantics (incremental vs full replacement), clearing mechanisms (empty string/null), and safety warnings ('DELETE all variants with that value'). Discloses response format ('compact preview with active_rules') absent from output schema.

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

Conciseness4/5

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

Information-dense with zero waste—every clause explains critical behavior (merge logic, deletion warnings, response format). Slight deduction for monolithic paragraph structure that could benefit from formatting breaks between rule families.

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?

Comprehensive for a high-complexity tool (13 params, nested JSON structures). Compensates for missing output schema by describing return value. Covers edge cases (clearing fields, removing families, variant deletion) essential for correct invocation.

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?

Despite 100% schema coverage, adds substantial value for complex rules_json parameter by documenting JSON structure, merge behavior, and specific option_edits action syntax with examples (rename_option, remove_value, etc.). Explains interaction patterns between rule families.

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?

Specific verb 'Update' with clear resource 'pricing, content, images, or variant rules' on 'already-imported product' effectively distinguishes from sibling tools like dsers_product_import (create) and dsers_product_preview (view).

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

Usage Guidelines4/5

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

Implicitly establishes prerequisite via 'already-imported product' and job_id requirement, indicating this follows dsers_product_import. Lacks explicit naming of alternatives (e.g., when to use dsers_rules_validate instead), but provides sufficient context for correct sequencing.

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

Update Rules on Imported Product

Instructions

Input Schema

Tool Description Quality Score

Other Tools

Latest Blog Posts

MCP directory API