Server prompt: create a page with generated media

Request create_page_with_generated_media; its optional argument is page_goal.

The prompt coordinates two distinct systems: the AI client creates the image, while POM AI’s WordPress tools import it and place its durable attachment ID or URL in supported page markup. It tells the client to read the media and builder resources, plan the required image roles, upload each asset, add metadata, inspect the relevant shortcode schema, validate the page, and then save.

Example:

{
  "name": "create_page_with_generated_media",
  "arguments": {
    "page_goal": "Create a draft services page with an accessible hero image"
  }
}

What to provide separately

State the factual content, brand constraints, prohibited imagery, usage rights, required aspect ratios, alternative-text intent, and whether a featured image is needed. Do not put license keys, private customer images, or unpublished personal information in the generation request.

The imported attachment and page are separate writes. Ask for both dry runs where available and verify both objects afterward. The page should reference the final WordPress attachment, not a temporary generation URL.

Review the image for accuracy, artifacts, rights, sensitive content, crop behavior, and meaningful alternative text. Page validation cannot perform those editorial checks.

Related guides: media authoring resource, media tools, and image safety review.