Skip to main content
Glama

woo_helper_update_stripe

Updates Stripe express checkout settings through cvrt-woo-helper, changing only the keys you provide. Maps button types to product, cart, and checkout pages; returns 409 when the Stripe Gateway plugin is inactive.

Instructions

Change Stripe express checkout through cvrt-woo-helper. Only the keys given change. locations maps a button type (apple_google_pay, link, amazon_pay) to the pages it shows on (product, cart, checkout). 409 when the Stripe Gateway plugin is inactive.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "woo_helper_update_stripe"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
locationsNoPages per button type
express_checkoutNoExpress checkout buttons on/off
scripts_checkout_onlyNoLoad Stripe.js only on the checkout page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavior: partial-update semantics ('Only the keys given change') and a specific failure mode (409 when the Stripe Gateway plugin is inactive). It omits what the response looks like and whether changes are reversible, which keeps it short of a 5.

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?

Four short sentences, front-loaded with purpose, then update semantics, then the nested parameter, then the error case. Every sentence carries information, though the phrasing is terse enough that 'cvrt-woo-helper' reads as internal jargon.

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?

Covers what an agent needs to call this correctly for a 4-parameter, nested-object mutation with no annotations and no output schema: scope, partial-update contract, nested mapping shape, and the blocking precondition. Only the returned payload remains undocumented, which is a minor gap without an output schema.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description earns above that by explaining the nested 'locations' object as button-type-to-pages mapping and enumerating the three button keys, clarifying the $ref-flattened schema. The two boolean flags are left to their schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Change Stripe express checkout through cvrt-woo-helper.' The mutation intent is unambiguous and reads distinctly against the read-oriented siblings (woo_helper_get_stripe, woo_helper_stripe_status), though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers mutation semantics ('Only the keys given change') and one precondition ('409 when the Stripe Gateway plugin is inactive'), which imply the safe usage context. It does not say when to reach for this instead of woo_helper_update_settings or the get/status siblings, leaving routing to inference.

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

Deploy Server

Other Tools