Whatalo

Returns the full category record for the given category ID. All 5 category fields are included in the response. NOTE: A missing category ID may trigger an upstream 5xx error rather than 404.

category_get

Returns the full customer record for the given customer ID. All 14 customer fields are included in the response. NOTE: A 404 response body may contain code VALIDATION_ERROR — this is a known API quirk; the tool maps by HTTP status. A missing customer ID may trigger an upstream 5xx error rather than 404.

customer_get

Returns the full order record for the given order ID. All 22 fields are included in the response, including nested customer, shipping_address, and items. Guest orders may omit customer and shipping_address. NOTE: A 404 response body code is uncertain for orders — the tool maps by HTTP status. A missing order ID may trigger an upstream 5xx error rather than 404. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

order_get

Returns the full product details for the given product ID, including variants when the API provides them. NOTE: A missing product ID may trigger an upstream 5xx error rather than 404. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

product_get

Returns the full inventory snapshot for the given product ID: product ID, SKU, tracking status, stock quantity, low-stock threshold, continue-selling status, and variant-level inventory when the API provides variants. NOTE: inventory uses continue_selling_when_out_of_stock (long name) distinct from product.continue_selling. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

product_inventory_get

Returns information about the merchant store associated with the credential forwarded by the MCP client. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

store_get

Returns a paginated list of categories with optional search filtering. per_page is clamped to a maximum of 100; omit or set to 0 to use the default of 25. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

category_list

Returns all line items for the given order ID. Each item includes a unique id and created_at, unlike the items returned by order_get.

order_items_list

Returns a paginated list of orders with optional status filtering. per_page is clamped to a maximum of 100; omit or set to 0 to use the default of 25. Optional filters: status (array: pending|confirmed|processing|shipped|delivered|cancelled|refunded), payment_status, customer_id, date_from, date_to, total_min, total_max, updated_at_from, updated_at_to, city, province, country, country_code, sort (order_number|total|created_at|updated_at|customer_name), order (asc|desc). Date filters (date_from, date_to, updated_at_from, updated_at_to) must be RFC3339 date-time values; local timezone offsets are normalized to UTC ending in Z (for example 2026-06-04T00:00:00-04:00 becomes 2026-06-04T04:00:00.000Z), and date-only values are not accepted. Aggregation: set group_by=by_day with date_from+date_to+timezone (IANA) to get daily order totals instead of a list. timezone is only used for MCP-side group_by=by_day bucketing; it is not sent to the Whatalo Orders API. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

order_list

Returns a paginated list of products with optional filtering by status (active|draft|archived|all), category (array), featured status, price range (price_min, price_max), stock status, and search query. per_page is clamped to a maximum of 100; omit or set to 0 to use the default of 25. sort accepts: name|price|created_at|updated_at|stock_quantity. Aggregation: set group_by=by_price_range to get product counts distributed across 5 fixed price buckets instead of a list. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

product_list

Returns a paginated list of customers with optional free-text search and sort. per_page is clamped to a maximum of 100; omit or set to 0 to use the default of 25. The search parameter is forwarded as ?search= to the Whatalo API. IMPORTANT: This tool presents the primary data in a visual widget the user can see. Do not restate it in text. Use your response only for interpretation, caveats, or next steps.

customer_search

Partially updates a category. Only fields you provide are changed; omitted fields remain unchanged. Uses PATCH semantics.

category_update

Updates an order's status, payment_status, and/or internal_notes via PATCH. All three fields are optional — provide only what you want to change. Idempotent: setting the same value twice returns the same result. Returns the full updated order with extended fields including is_cancellable, is_fully_paid, and completed_at.

order_status_update

Partially updates a product. Only fields you provide are changed; omitted fields remain unchanged. Uses PATCH semantics. To add or change images, do NOT pass base64 data or an external URL in main_image or description — use product_image_upload with the product_id instead; it uploads to Whatalo and sets the gallery, main image, or description image. main_image only accepts a Whatalo CDN URL already produced by product_image_upload.

product_update

THIS is the tool to add or upload any image to a product — for the gallery, the main image, or images inside the description. Requires an existing product_id: to create a product with images, call product_create first, then call this with the new product_id. Provide each image as base64 image_data OR an image_url; the server performs the full upload and always hosts the file on Whatalo's CDN. Prefer image_url whenever the image is available at a URL: passing the URL is far faster than sending base64, and the server downloads and re-hosts it on Whatalo — use image_data only for raw bytes with no URL. Some MCP clients attach files directly instead of giving you base64 or a URL — when your input already includes a file reference with download_url/file_id, pass it via files instead of images, and set target/is_main/alt through file_options, since a file item can carry only the four fields the host fills. If you have neither a file reference, a URL, nor bytes for the image, ask the user for one instead of guessing. Upload the original file as-is: do not resize, compress, or re-encode it; only if a file exceeds the size limit (20 MB image, 50 MB video) compress it just enough to fit. Choosing target: product photos and catalog images usually belong in the gallery (max 15 per product); images that are part of rich, written description content usually belong embedded in the description. These are defaults to guide your judgment — explicit user instructions ALWAYS win. Images embed at full width by default: never invent width or height, omit them unless the user asks for a specific size. Each image succeeds or fails independently; every successful result returns its public_url and media_id so you can reference or remove it later without another call. Allowed types: jpeg, png, webp, avif, mp4, webm, quicktime.

product_image_upload