Skip to main content
Glama
OyaAIProd

DSers MCP Product

by OyaAIProd

Update Rules on Imported Product

dsers_product_update_rules

Update pricing, content, images, or variant rules on imported products. Merge rules incrementally to adjust titles, prices, images, and options without losing existing data.

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
NameRequiredDescriptionDefault
job_idYesJob ID from a previous dsers_product_import call.
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.
target_storeNoStore ID or name from dsers_store_discover.
title_prefixNoFlat param: prepend to product title.
title_suffixNoFlat param: append to product title.
title_overrideNoFlat param: replace entire product title.
visibility_modeNobackend_only (default, safe) or sell_immediately (live — confirm with user).
pricing_multiplierNoFlat param: multiplier value when pricing_mode='multiplier'.
pricing_fixed_priceNoFlat param: exact price in dollars when pricing_mode='fixed_price'.
pricing_fixed_markupNoFlat param: markup in dollars when pricing_mode='fixed_markup'.
description_append_htmlNoFlat param: append HTML to description.
description_override_htmlNoFlat param: replace full description (HTML).
Behavior5/5

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

The description goes well beyond annotations by disclosing merge semantics (replace-by-family vs field-merge), the use of null to remove entire families, the full replacement of option_edits, and the destructive delete of variants for remove_value. This provides critical side-effect visibility beyond the generic destructiveHint=false.

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?

The description is dense but efficiently structured: purpose, merge rules, clearing/removal, option_edits actions, and response format. Each sentence contributes unique information, making it appropriately sized for the tool's complexity.

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?

The description covers operational behavior, edge cases for clearing/removing, all option_edits actions, and the response shape. Combined with the rich schema, it is comprehensive for a tool with 13 parameters, no output schema, and complex merge logic.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds substantive semantics for rules_json: explaining merge behavior, clearing fields with empty string/null, removing families via null, and the DELETE consequence of remove_value. These details are not fully captured in the schema description, raising the value beyond the baseline.

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 opens with a clear, specific action: 'Update pricing, content, images, or variant rules on an already-imported product.' It identifies the resource (rules on an imported product) and disambiguates from sibling tools like import or preview by focusing on updates.

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?

The description provides strong context for when to use ('already-imported product') and detailed how-to guidance (merge behavior, clearing, removal of families). However, it does not explicitly name alternative tools or state when not to use it, leaving the distinction to the reader.

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/OyaAIProd/dsers-mcp-product'

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