mailerpress/list-tags returns a paginated list of MailerPress tags, with optional free-text search on the name.
Every tag ID and name returned here is safe to reference in the contact-writing abilities.
At a glance
| Ability | mailerpress/list-tags |
| Toolset | MailerPress — toolset/mailerpress |
| Group | MailerPress › Tags |
| Requires | AcrossAI Pro, plus MailerPress 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
That guarantee is the point of reading this first. Tag IDs passed to mailerpress/create-contact or mailerpress/update-contact that do not exist are not necessarily refused, and a contact tagged with nothing looks identical to one tagged successfully.
Tags are the segmentation mechanism, as against lists which are the consent mechanism. A tag records something decided about a contact — customer, trial user, attended the webinar — rather than something they subscribed to.
They are also what workflow triggers most often key on. A tag applied is a common automation entry point, which makes tag names load-bearing in a way list names usually are not.
Tags accumulate faster than lists, because applying one is cheap and nothing prunes them. A site running for a few years has tags nobody remembers creating.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
search | string | No | Free text over the tag name. |
per_page | integer | No | Rows per page. |
What comes back
| Name | Type | What it is |
|---|---|---|
tags | array | Each tag with its ID and name. |
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 tags do we use?
It resolves to one call:
{
"ability": "mailerpress/list-tags",
"parameters": {}
}Worth knowing
- Read these before passing tag IDs to a contact write.
- Tags are for segmentation; lists are for consent.
- Workflow triggers frequently key on a tag being applied.
- Tags accumulate and nothing prunes them.
Related abilities
- MailerPress Create Tag — add one
- MailerPress Find Workflows Using — what depends on one
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category