Home / Token cost / WooCommerce Store Manager

The WooCommerce Store Manager MCP server costs 3,555 tokens before the first call.

Connect WooCommerce Store Manager and its 47 tool definitions are loaded into the model's context on every request — 1.8% of a 200k window spent before your agent does anything.

QUICK ANSWER The WooCommerce Store Manager MCP server's tool definitions consume 3,555 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 47 tools · 3,555 tokens · 1.8% of 200k · 0.4% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 1.8%
1M WINDOW 0.4%

Corpus context: WooCommerce Store Manager ranks #1217 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 3,555 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 76 tokens per tool.

ToolCategoryTokens% of server
wc_product_create Write 390 11.0%
wc_order_create Write 261 7.3%
wc_product_update Write 252 7.1%
wc_products_list Read 213 6.0%
wc_coupon_create Write 166 4.7%
wc_orders_list Read 147 4.1%
wc_variation_create Write 127 3.6%
wc_customers_list Read 120 3.4%
wc_order_update Write 104 2.9%
wc_refund_create Financial 93 2.6%
wc_analytics_products Read 93 2.6%
wc_variation_update Write 76 2.1%
wc_customer_create Write 75 2.1%
wc_products_batch Destructive 74 2.1%
wc_category_create Write 74 2.1%
wc_webhook_create Write 71 2.0%
wc_analytics_revenue Read 63 1.8%
wp_posts_list Read 62 1.7%
wc_reports_sales Read 60 1.7%
wc_coupons_list Read 59 1.7%
wc_categories_list Read 57 1.6%
wc_tax_rates_list Read 52 1.5%
wc_variations_list Read 51 1.4%
wc_tags_list Read 50 1.4%
wc_order_note_create Write 50 1.4%
wc_reports_top_sellers Read 46 1.3%
wp_media_upload Write 46 1.3%
wc_webhooks_list Read 45 1.3%
wc_setting_update Write 42 1.2%
wc_coupon_delete Destructive 39 1.1%
wc_order_delete Destructive 39 1.1%
wc_product_delete Destructive 39 1.1%
wc_order_notes_list Read 31 0.9%
wc_shipping_zone_methods Read 31 0.9%
wc_system_status_tool_run Read 31 0.9%
wc_product_get Read 30 0.8%
wc_settings_get_group Read 30 0.8%
wc_customer_get Read 28 0.8%
wc_order_get Read 28 0.8%
wc_reports_orders_totals Read 28 0.8%
wc_reports_customers_totals Read 27 0.8%
wc_shipping_zones_list Read 27 0.8%
wc_reports_products_totals Read 26 0.7%
wc_settings_list_groups Read 26 0.7%
wc_system_status_tools Read 26 0.7%
wc_tax_classes_list Read 26 0.7%
wc_system_status Read 24 0.7%

Most agents use a handful of these tools. They pay for all 47.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (76 tokens each).

Grant scopeDefinition costReduction
All 47 tools (no gateway) 3,555 tokens
3 granted tools ~227 tokens −94%
5 granted tools ~378 tokens −89%
10 granted tools ~756 tokens −79%

WooCommerce Store Manager token-cost questions.

How many tokens does the WooCommerce Store Manager MCP server use?+

Its 47 tool definitions total 3,555 tokens — 1.8% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does WooCommerce Store Manager consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce WooCommerce Store Manager's token usage?+

Expose fewer tools. A PolicyLayer grant scopes WooCommerce Store Manager to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 227 tokens, a 94% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 47 catalogued WooCommerce Store Manager tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes WooCommerce Store Manager to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.