pom://shortcodes: available shortcode catalog

Read pom://shortcodes when a POM builder page needs a component and you do not yet know its exact shortcode tag. It is a compact availability list, not the full parameter reference.

What the resource returns

The JSON payload contains:

• items: shortcodes usable in the current site runtime;
• total: the number of returned items;
• rules: general authoring rules for the catalog.

Each item identifies the shortcode, visible label, description, source, optional POM Theme module, category, container status, and enabled state. The catalog combines structural builder tags, registered WordPress shortcodes, builder component maps, and enabled POM Theme modules. It is sorted by tag so clients can make deterministic selections.

Availability matters more than memory. A shortcode documented on another site may be absent because its plugin or POM Theme module is not active here.

Recommended workflow

1. Read pom://site/authoring-context to understand the target editor and layout model.
2. Read pom://shortcodes.
3. Select the narrowest component that meets the content requirement.
4. Read pom://shortcodes/{tag} for that component’s live attributes.
5. Compose the complete nested markup.
6. Call pom_validate_builder_content.
7. Write only after validation has no errors.

If the catalog is too broad, use the pom_get_available_shortcodes tool instead. That tool can filter by scope, target post type, and inactive status; the resource always returns the default available catalog.

What not to infer

An empty attribute list means POM AI could not derive builder parameters for that registered shortcode; it does not mean arbitrary attributes are supported. Likewise, an item being present does not prove it is appropriate at the root of a page. Parent-child rules and discouraged legacy components are checked by the builder validator and the authoring context.

Related guides: individual shortcode resources, POM builder guide, and shortcode authoring tools.