POM authoring tool reference

Ten read-only tools that tell an MCP client how a POM site should be edited, before it writes anything. They are the difference between generated content that works and generated content that merely looks like it should.

The tools

All ten are read-only and have no write gate. Normal authentication, capabilities and request limits still apply.

Two scope groups

The split follows the work: page content is a content permission, templates are a theme permission. A client that can edit pages cannot necessarily inspect templates.

The two workflows they serve

Building page content

Read the context and existing source first. For Gutenberg, follow block editor authoring, including the installed browser serializer and an actual editor save. For an existing Classic Builder document:

1. pom_get_authoring_context
2. pom_get_available_shortcodes
3. pom_get_shortcode_schema for each shortcode you will use
4. Compose
5. pom_validate_builder_content
6. Fix, re-validate
7. Write with a content tool

Building a template

1. pom_get_template_schema
2. pom_get_available_mergetags
3. Compose
4. pom_validate_template_markup
5. Fix, re-validate
6. Write with pom_theme_upsert_html_template

Steps 2, 3 and 5 are the ones an assistant skips unless told. See Validate builder or template markup before writing.

Why guessing fails

POM classic builder content is nested shortcodes, and the vocabulary is specific to this site: which modules the theme enables, which attributes each accepts, and which nesting is legal.

An assistant composing from general knowledge produces markup with plausible attribute names that are silently ignored, modules that do not exist, and columns outside rows. MCP content writes reject violations of the target palette, while incomplete attribute contracts still require inspection before relying on their behavior.

The schema tools remove the guessing; the validators catch what remains.

Errors are not the only output

The validators return valid, issues and a summary. Shortcode/template results include suggested next steps; block validation additionally identifies its server scope and the remaining browser check. Issues carry a severity:

• error — the content is invalid; valid is false and you should not write.
• warning — inspect the reported limitation or decision; this does not prove that an attribute works.

Warnings are worth reading rather than dismissing. They are how the layer tells you a page is using a discouraged element, or leaning on inline styles instead of the shortcode attributes that exist for the job.

Related layers

Resources carry the longer-form guidance the context tool points at — the builder documentation, layout and content-model guides, per-context template and merge-tag references. See MCP resources.

Prompts encode whole workflows including these tools in the right order. Where one covers your job, start from it. See Prompt recipes.

Related

• Build POM builder content

• Create and assign POM Theme templates

• Theme template tools

• Build pages with the installed block editor