Catalog QA Desk
Check product CSVs and feeds
Check an online store's product catalog before you import it or send it to a shopping feed. Ask "will this Shopify product CSV import cleanly?", "what would Google Merchant Center reject in my catalog?", "which products have no image alt text or a copied description?" or "write me a sheet that fixes the empty alt text". Catalog QA Desk checks a Shopify product CSV against the import rules (required columns, handles, options, duplicate variants, prices, statuses, image URLs, barcodes mangled by a spreadsheet) and returns the rows that block the import and the ones that import wrongly, each with the fix. It checks products for Google Merchant Center feed rules: missing or invalid barcodes (GTIN length and check digit), titles that are too long, promotional or in capitals, missing descriptions, links in descriptions and missing images. It audits listing text: images without alt text, descriptions copied between products, thin descriptions and title problems; and it builds an advisory CSV of corrected titles and alt text for you to review and import yourself. You can pass the CSV text (up to 2 MB), or a store address: the store's public product feed (/products.json, at most 5 pages of 250 products) is read once, after its robots.txt, only when you ask. Large stores often block that feed, and then a CSV is needed. It does not use the Shopify admin API, does not log in to any store, changes nothing in a store and does not submit anything to Google. Nothing you send or read is stored, no catalog is kept or indexed, and there is no account; only a daily count of calls per tool is recorded.
What you can ask
- Will this Shopify product CSV import cleanly?
Example path →
MCP connector
- Server URL
https://catalogqa.openkrill.app/mcp- Login
- None
- Protocol
- MCP 2026-07-28
- Instructions
Catalog QA Desk: Check product CSVs and feeds. Nothing is stored: a file or feed is used for one answer and dropped, so pass the full text on every call. Use with the text of a Shopify product CSV before an import: report blocking items first, then warnings, naming row and fix; it checks barcodes too, so no second call is needed for them. Use and with either csv (the file text) or domain (a store address), never both; domain reads the store's public product feed once and a large store may refuse it, in which case ask for the CSV. Use to produce a CSV of corrections; it is advisory text for the user to review and import themselves, nothing is changed in the store. Counts in totals are before lists were cut; say so when truncated is true. Do not call a GTIN valid beyond its check digit. When a store refuses its feed, ask the user to export the CSV from Shopify admin (Products > Export). A CSV over 2 MB is refused with csv_too_large: split it by rows, header row in each part. Use when the user has a photo of an item to sell: present brand and model as facts only when filled, present likely_brand as a guess to confirm, and ask the seller the ask_seller questions before publishing; it refuses photos of people. This server allows 60 tool calls a minute per network and 5,000 a day for all callers together; the day count resets at 00:00 UTC. If a tool fails, gives a wrong answer, or a tool you need is missing, call with one short message (kind, message, tool); reads the answer.
Tools
Reads data6
Changes data1
Skills
None in the store listings or on the server