geodirectory/list-directory-pages returns the WordPress page backing each GeoDirectory role: Add Listing, Search, Location, CPT Archive, Archive Item, and the single-listing Details page.
Each comes with its ID, title, edit link, and whether it still contains GeoDirectory blocks.
At a glance
| Ability | geodirectory/list-directory-pages |
| Toolset | GeoDirectory — toolset/geodirectory |
| Group | GeoDirectory › Directory & Pages |
| Requires | AcrossAI Pro, plus GeoDirectory 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 directory page works because it contains the right GeoDirectory blocks. Edit one in the block editor, remove a block by accident, and the page still exists and renders — as an ordinary page with nothing on it.
That failure is invisible from the page list and obvious here, which is why the check is reported per role.
The per-listing-type overrides are the other half. A multi-directory site can point the Add Listing role at a different page per type, and the override beats the site-wide value — so reading only the site-wide assignment describes a page that may not be in use.
Run this before editing any directory page, and again after.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
post_type | string | No | Report the per-listing-type overrides for this type. Defaults to the site default. |
What comes back
| Name | Type | What it is |
|---|---|---|
pages | object | Each role with its page ID, title, edit link and block status. |
overrides | object | Per-listing-type page overrides. |
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:
Which pages are our directory pages?
It resolves to one call:
{
"ability": "geodirectory/list-directory-pages",
"parameters": {}
}Worth knowing
- A directory page with no GeoDirectory blocks renders as an empty page.
- Per-type overrides beat the site-wide assignment.
- Run it before and after editing a directory page.
- Read-only.
Related abilities
- GeoDirectory Assign Directory Page — point a role elsewhere
- GeoDirectory List Display Blocks — the blocks these need
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category