geodirectory/list-display-blocks returns every GeoDirectory block available for building directory pages, with its block name, shortcode, purpose, and ready-to-insert block markup.
Call it before editing any directory page, because these blocks cannot be discovered any other way.
At a glance
| Ability | geodirectory/list-display-blocks |
| Toolset | GeoDirectory — toolset/geodirectory |
| Group | GeoDirectory › Tabs, Sorting & Blocks |
| 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
GeoDirectory registers its blocks at runtime from JavaScript rather than in PHP. That means they do not appear in the WordPress block registry, and nothing server-side can enumerate them — including every generic block ability.
So an assistant building a directory page without this read is guessing at block names, and a wrong block name produces markup WordPress renders as an invalid block.
The ready-to-insert markup is the practical output. It is the block comment and attributes in the shape the editor expects, which can be written straight into a page.
The shortcode equivalent comes with each, which is the fallback for themes and page builders that are not block-based.
The group filter narrows to the blocks that belong on one kind of page — archive, search, single listing, or the add-listing form — which is usually what you want, since a search block on a single-listing page does nothing useful.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
group | string | No | Only blocks belonging to this page role. |
search | string | No | Free-text filter across name, shortcode and purpose. |
What comes back
| Name | Type | What it is |
|---|---|---|
blocks | array | Each block with its name, shortcode, purpose and ready-to-insert markup. |
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 blocks do I need to build a directory search page?
It resolves to one call:
{
"ability": "geodirectory/list-display-blocks",
"parameters": {
"group": "search"
}
}Worth knowing
- These blocks are registered from JavaScript and are invisible to the block registry.
- No generic block ability can enumerate them.
- The markup is ready to insert into a page.
- Read-only.
Related abilities
- GeoDirectory List Directory Pages — which pages need them
- GeoDirectory Assign Directory Page — make the page live
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category