Skip to main content
Glama

woo_helper_update_emails

Update WooCommerce email styling by changing only the specified fields; invalid values are rejected with a clear error naming the field.

Instructions

Change the WooCommerce email look through cvrt-woo-helper 0.2.0+. Only the keys given change; an invalid value is a 400 naming the field and nothing is written. Returns the settings as woo_helper_get_emails does.

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_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
logo_idNoMedia library attachment id of the logo; 0 removes it
base_colorNoBase (accent) colour
link_colorNoLink colour; empty = WooCommerce's default
logo_widthNoLogo width in px (40-200)
text_colorNoBody text colour
footer_textNoFooter text; placeholders {site_title} {site_url} {store_address} {store_email} {year}
product_imagesNoProduct images in order emails
background_colorNoEmail background colour
footer_text_colorNoFooter text colour
body_background_colorNoBody background colour
certificate_link_onceNoShow the certificate download link only once (needs wp-woo-pdf-builder 1.7.6+)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.9/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 does well: it discloses partial-update semantics, atomic validation behavior (a 400 naming the offending field with nothing written), a plugin version gate, and where the return payload is documented. It stops short of covering permissions or whether prior values are recoverable.

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

Conciseness5/5

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

Three tight sentences with the action front-loaded, followed by update semantics, error contract, and return shape. Every sentence contributes distinct information and there is no filler.

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?

For a 12-parameter mutation with no output schema and no annotations, the definition covers the essentials: partial-update behavior, the atomic validation contract, a version requirement, and a pointer to the read tool for the response shape. Auth/permission context is the main remaining gap.

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 description coverage is 100%, so a 3 baseline applies, and the description adds genuine meaning by establishing patch semantics for the otherwise optional 12 parameters and by explaining the failure mode tied to any single invalid value. It does not clarify the less obvious fields, but the schema already documents those thoroughly.

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?

The description uses a specific verb ('Change') and names the resource ('WooCommerce email look'), scoping it to appearance settings and naming the backing plugin/version. It is clearly distinguishable from sibling reads like woo_helper_get_emails and from the broader woo_helper_update_settings, though it does not explicitly say which sibling to prefer.

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?

Usage context is implied: it is the mutation counterpart to woo_helper_get_emails and applies to email styling. The patch semantics ('only the keys given change') tells the agent a minimal payload is acceptable, but there is no explicit statement of when to use this versus woo_helper_update_settings or of any prerequisites.

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