Skip to main content
Glama

woo_helper_get_emails

Retrieves WooCommerce email settings, including logo URL/format warnings, width, colors, footer text, product images, certificate link, and environment details to verify and troubleshoot templates.

Instructions

WooCommerce email look managed by cvrt-woo-helper 0.2.0+: logo (id, url, warning for unsafe formats), logo width, colours, footer text, product images, certificate link once, plus the environment (WooCommerce version, email template improved/classic/block_editor, PDF builder).

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose that a 'warning for unsafe formats' may be returned and that environment details (WooCommerce version, template mode, PDF builder) are included, which is useful beyond structured fields. However, it says nothing about permissions, whether any state is touched, or how the 'certificate link once' value behaves. It is a read operation by implication of 'get', not by explicit statement.

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

Conciseness3/5

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

It is a single sentence with no filler, but it is a dense parenthetical list that reads as a field dump rather than a front-loaded statement of purpose. A leading clause such as 'Read the current WooCommerce email appearance settings' would have made the enumeration scannable.

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

Completeness3/5

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

With no output schema, the enumeration of returned fields is genuinely necessary and mostly covers the return payload, including the environment block. What is missing is any framing of the read/write relationship with woo_helper_update_emails and any indication of when the returned 'warning' should matter. Adequate but with clear gaps for a settings-read tool.

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% with a single required 'site' parameter whose description already points to list_sites. The description adds nothing about the site parameter or its format, so baseline 3 applies.

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

Purpose3/5

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

The description enumerates what the tool surfaces (logo, logo width, colours, footer text, product images, certificate link, environment/template mode), so an agent can infer it reads the current email appearance settings. But it is a run-on noun phrase with no verb, and the name 'get_emails' risks being read as 'list emails' rather than 'read email template settings'. It also never explicitly distinguishes itself from the sibling woo_helper_update_emails.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no statement of the situation that calls for reading email settings, and no pointer to woo_helper_update_emails as the write counterpart. The only usage signal is the implicit 'get' in the name. An agent must infer the get/update pairing from sibling names alone.

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