mailerpress-pro/list-segment-condition-metadata discovers the condition types, operators and value shapes usable in a segment’s conditions payload.
Read it before authoring a create or update call.
At a glance
| Ability | mailerpress-pro/list-segment-condition-metadata |
| Toolset | MailerPress Pro — toolset/mailerpress-pro |
| Group | MailerPress Pro › Segments |
| Requires | AcrossAI Pro, plus MailerPress with its Pro add-on active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
A segment condition is a type, an operator and a value — and all three come from a fixed vocabulary that depends on what this install has. A site with WooCommerce has purchase conditions; one without does not.
Sending a type MailerPress does not recognise produces invalid_conditions rather than a segment that matches nothing, which is the right behaviour and does not tell you what would have been valid.
This does. It is the difference between writing a segment in one call and discovering the vocabulary through a series of rejections.
The value shape matters as much as the type. Some operators take a scalar, some take a list, some take a date expression — and an operator paired with the wrong shape is the same rejection.
Read-only and cheap.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
condition_types | array | Each type with its operators and the value shape each operator expects. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What can I build a MailerPress segment out of?
It resolves to one call:
{
"ability": "mailerpress-pro/list-segment-condition-metadata",
"parameters": {}
}Worth knowing
- The vocabulary depends on what is installed — WooCommerce adds purchase conditions.
- An unrecognised type is rejected, not silently unmatched.
- The value shape varies by operator.
- Read-only.
Related abilities
- MailerPress Pro Create Segment — what this is for
- MailerPress Pro Segment Product Values — the product values for purchase conditions
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category