Skip to main content
Glama

WooCommerce store product export

woocommerce_store_products
Read-only

Export WooCommerce product data from one or more stores via the public Store API to run competitor price checks, catalog research, or find discounted items.

Instructions

Export products from one or more WooCommerce shops through WooCommerce's public Store API: name, SKU, price, regular and sale price, currency, stock, rating, categories, attributes and images. Optional search term and sale-only filter. Use it for competitor price checks, catalog research or finding discounted items on WordPress/WooCommerce stores. Runs the Apify Actor loudtzu/woocommerce-store-products on your own Apify account (pay per event: $0.0005 per run + $0.00026 per product, billed by Apify; Apify platform usage may apply). Store page: https://apify.com/loudtzu/woocommerce-store-products

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "woocommerce_store_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoSearch (optional). Only products matching this text, using the shop's own search.
storeUrlsNoStore URLs. One WooCommerce shop per line, e.g. 'https://shop.example.com'. Only the site address is used. Empty lines stop the run before anything is charged. If you leave this out, the Actor reads mercantile.wordpress.org (the official WordPress swag shop). Example: ["https://mercantile.wordpress.org"]
onSaleOnlyNoOn sale only. Only products the shop marks as on sale.
runOptionsNoOptional run limits (not passed to the Actor). maxTotalChargeUsd caps what this single call can cost you on Apify.
includeDescriptionNoInclude descriptions. Add short and full descriptions as plain text (emails and phone numbers removed).
maxProductsPerStoreNoMax products per store. Stop after this many products from each shop (default 100, max 50,000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already carry readOnly/openWorld/destructiveHint, and the description adds genuinely useful operational context beyond them: it runs on the caller's own Apify account, exact per-event pricing ($0.0005 per run + $0.00026 per product), possible platform usage fees, and the default fallback to mercantile.wordpress.org. It does not discuss result volume, pagination, or error/failure behavior, so it isn't exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with capability and field list, then triggers, then cost and Actor identity. The field enumeration and pricing parenthetical are dense but each carries selection-relevant information; the store URL at the end is the only line that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six optional parameters, a nested options object, and no output schema make costing and default behavior the key unknowns, and the description covers both (per-product charge, maxTotalChargeUsd context, default site when storeUrls is omitted). What's missing is an indication of the response shape and volume — though maxProductsPerStore in the schema partly covers volume.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter is documented there, including the nested runOptions charge cap and the default store. The description only restates the optional search term and sale-only filter, adding no syntax or semantics beyond the schema; baseline 3 applies.

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?

States a specific verb (export) and resource (products) and pins the source to WooCommerce's public Store API, which cleanly separates it from the Shopify/Best Buy siblings. The enumeration of returned fields (SKU, price, stock, categories, images) tells an agent exactly what data it gets without opening the schema.

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?

Gives concrete use cases: competitor price checks, catalog research, finding discounted items on WordPress/WooCommerce stores. It does not name a when-not condition or point at an alternative sibling, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.