geodirectory/get-listing fetches one listing by ID, including every custom field its listing type defines.
Address and coordinates, business hours, categories and tags, rating, and any site-defined fields.
At a glance
| Ability | geodirectory/get-listing |
| Toolset | GeoDirectory — toolset/geodirectory |
| Group | GeoDirectory › Listings |
| 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
The listing type has to match. GeoDirectory routes by type, so asking for a listing under the wrong one returns a 404 rather than the listing — and on a multi-directory site that is easy to do. Omitting the type uses the site default, which may not be the right one.
The edit context is the other thing worth knowing. Fields marked for-admin-use are omitted from the default view context, so a field that exists and holds data can be absent from a read that looks complete.
Those fields are usually internal — a verification note, an owner’s account reference — and their absence is correct for a public read and wrong for an audit.
Images come back as objects, which is worth remembering before an update: they are written as strings, so a read cannot be fed straight back in.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | Listing post ID. |
post_type | string | No | Listing type, for example gd_place. Defaults to the site default. See geodirectory/get-directory-overview for the valid values. |
context | string | No | Use edit to include admin-only fields. |
What comes back
| Name | Type | What it is |
|---|---|---|
listing | object | The listing with every field its type defines. |
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:
Show me everything about listing 812.
It resolves to one call:
{
"ability": "geodirectory/get-listing",
"parameters": {
"id": 812,
"context": "edit"
}
}Worth knowing
- A mismatched listing type 404s rather than returning nothing.
- Admin-only fields need
context: edit. - Images read as objects and write as strings — a read does not round-trip.
- Read-only.
Related abilities
- GeoDirectory Update Listing — change it
- GeoDirectory Get Listing Package — which fields it may use
- GeoDirectory List Listing Fields — what the fields mean
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category