Improve Product Titles and Descriptions with AI
Use existing product facts to draft clearer text, then review the exact change before asking the AI to apply it.
Prerequisites
First complete a read-only connection check. A provider write needs a paid write entitlement, write permission, the selected store in scope and its specific capability. Review exact store, item and proposed values. Ordinary writes do not each require Store MCP browser approval.
Steps
- Read listings.get for the chosen listing, including current text, variants and provider details.
- Ask for a proposed title and description using only verified facts. Mark unknown materials, measurements or certifications as questions.
- Review the before/after text and select one supported listing update. Use a new idempotencyKey for that deliberate mutation.
- Read the listing again and compare the exact saved text. If the outcome is unknown, inspect the receipt instead of trying a new key.
Safe example
The example uses synthetic names. Select your own authorized store and verify every identifier before a write.
For synthetic SKU DEMO-MUG, suggest a clearer title using only the current listing facts. Do not add materials, certifications or promises. Show the proposed text and wait for my review.You’re done when…
Expect a proposal first, then only the reviewed update when explicitly requested. Verify provider text with listings.get and inspect Activity for the operation outcome.
Limitations
AI copy does not guarantee rankings or sales. WooCommerce listing edits are limited to simple products; use returned schemas and store capabilities. No bulk atomic edit is promised.
Update product prices
Read the exact listing and variant and confirm its currency. Money uses a decimal-string amount and currency, not floating-point arithmetic in an inferred currency. Check whether the provider supports the requested listing/variant field before writing.
For a synthetic item: “Show the current price of the selected DEMO-MUG variant and propose 12.50 in its existing currency; wait for review.” After review, issue one supported listings.update, then read back price and variant. Treat each additional listing as a separate change; discounts and channel-specific pricing are not interchangeable with this field.