Every redirect belongs to a group, and a group decides which module serves it — WordPress, Apache or Nginx.
redirects/list-groups returns the groups a redirect can belong to, so you can place a new one in the right group or move an existing one.
At a glance
| Ability | redirects/list-groups |
| Toolset | Redirection — toolset/redirection |
| Group | Redirection |
| Requires | Redirection, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.43 and later |
How it works
Each group comes back with its id, name, module (WordPress, Apache or Nginx), redirect count and whether it is enabled. Use a group id when creating or moving a redirect.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
per_page | integer | No | Page size, 5–200 (default 50). |
page | integer | No | 1-based page number. |
direction | string | No | asc or desc by name (default asc). |
What comes back
| Name | Type | What it is |
|---|---|---|
groups | array | The groups with id, name, module, redirect count and enabled state. |
count | integer | How many were returned on this page. |
total | integer | How many groups there are. |
page | integer | The page returned. |
success | boolean | Whether the call completed. |
Example
Ask your assistant:
List the redirect groups.
It resolves to one call:
{
"ability": "redirects/list-groups",
"parameters": {}
}Worth knowing
- Read-only — it lists groups and writes nothing.
- A redirect must belong to a group; this is where you get the id to pass to Create Redirect.
- Needs the Redirection plugin active; without it you get a clear “not active” message.
Related abilities
- Create Redirect — place a redirect in a group
- Update Redirect — move a redirect to another group
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category