Skip to main content
Glama

Push Product to Shopify / Wix Store

dsers_store_push
Destructive

Push prepared product drafts to Shopify or Wix stores with safety checks that validate pricing, inventory, and margins before publishing.

Instructions

Push one or more prepared import drafts to the connected Shopify or Wix store(s). SAFETY: Automatic pre-push validation checks pricing (blocks if sell price < cost or $0) and stock (blocks if all variants have zero inventory). Warnings are raised for low margin (<10%), low stock (<5 units), or very low price (<$1). If blocked, fix pricing rules or use force_push=true ONLY after explaining the risk to the user. 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. SAFETY RESPONSE: If checks fail, response includes 'blocked' (array of reasons push was rejected — must fix before retrying) and/or 'warnings' (array of risk alerts — push proceeds but user should be informed). blocked = hard stop (e.g. sell below cost), warnings = soft alert (e.g. low margin). On success, returns per-job: job_id, status, target_store, visibility_applied, push_options_applied, job_summary, warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idNoSingle job ID from dsers_product_import. Used for single-push or multi-store mode.
job_ids_jsonNoBatch push: JSON array of job ID strings or objects {job_id, target_store?, target_stores?, push_options?, visibility_mode?}. Example: ["job-abc123", {"job_id": "job-def456", "target_store": "My Store"}]. When provided, this takes priority over job_id.
target_storeNoTarget store ID or display name from dsers_store_discover. Required when the account has multiple stores.
target_stores_jsonNoMulti-store: JSON array of store IDs or display names. Pushes the same job_id to each listed store. Example: ["Store A", "Store B"]
visibility_modeNoOverride the visibility mode set during prepare. backend_only: draft — SAFE. sell_immediately: published and LIVE — RISK: confirm pricing/inventory with user first.
push_options_jsonNoPush configuration as JSON string. Keys: publish_to_online_store (bool), image_strategy ('selected_only' or 'all_available'), pricing_rule_behavior ('keep_manual' or 'apply_store_pricing_rule'), shipping_profile_name (string — Shopify delivery profile name), auto_inventory_update (bool), auto_price_update (bool), sales_channels (string[]), only_push_specifications (bool). Example: {"image_strategy": "all_available", "shipping_profile_name": "DSers Shipping Profile"}
force_pushNoOverride pre-push safety checks. ONLY set true after you have shown the user the specific risk (e.g., 'This product is priced below cost — you will lose $X per sale') and they explicitly confirmed. Never set this silently.
Behavior5/5

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

The description adds substantial behavioral context beyond what annotations provide. While annotations indicate destructiveHint=true and non-idempotent behavior, the description details specific safety checks (pricing validation, stock validation), warning thresholds (low margin <10%, low stock <5 units), response structure (blocked vs warnings arrays), and the consequences of different visibility modes (backend_only vs sell_immediately). This significantly enhances the agent's understanding of the tool's operational behavior.

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 efficiently structured with clear sections: safety checks, three operational modes, and response format. Every sentence adds value—no redundant information or fluff. It's front-loaded with critical safety information, followed by operational details, making it easy for an agent to parse.

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?

Given the tool's complexity (7 parameters, destructive operation, multiple modes) and lack of output schema, the description provides comprehensive context. It covers safety mechanisms, operational modes, parameter interactions, and detailed response format. The description successfully compensates for the missing output schema by explaining what success/failure responses contain.

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 description coverage, the baseline would be 3, but the description adds meaningful context about parameter interactions and usage patterns. It explains how job_ids_json takes priority over job_id, clarifies the relationship between target_store and target_stores_json for different modes, and provides concrete examples of JSON structures. However, it doesn't fully explain all parameter combinations beyond what's implied in the three modes.

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 clearly states the specific action ('Push one or more prepared import drafts') and target resources ('to the connected Shopify or Wix store(s)'). It distinguishes this from sibling tools like dsers_product_import (which creates drafts) and dsers_product_update_rules (which modifies rules rather than pushing products).

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?

The description provides explicit guidance on when to use this tool versus alternatives: it specifies three distinct modes (single push, batch push, multi-store push) and when each applies based on parameter combinations. It also includes clear safety warnings about when to use force_push and when not to (e.g., 'ONLY after explaining the risk to the user').

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