Read an existing page

Use this workflow after your website and Agent are connected. Start with a demonstration website and a page whose title you can confirm in WordPress.

Before you start

Select the intended Workspace and website. Put the Agent in Read only mode. Confirm that the website's WordPress page-list and page-read Abilities are enabled. You do not need to enable high-impact Abilities.

Ask the Agent

Use MoraWP to list the websites I can access and let me choose one.
Discover its WordPress page-list and page-read Abilities, then inspect
their current input schemas. List pages and let me choose an existing page.
Read that page's title and content using execute_read_ability.
Use the returned identifiers. Do not change, publish, delete, run code,
or access files.

Verify the result

Compare the returned title and content with the same page in WordPress. Builder content or HTML can differ from the final visual layout; the identifier and target website should still match.

Check Activity for the actual Ability execution. Platform discovery does not appear as a customer Ability action. A dispatched read counts toward the Workspace's AI Actions allowance.

If it fails

A missing website needs a website-access review. A missing Ability needs fresh discovery and a check of the relevant Integration. For an invalid item, select it from the current website's list rather than guessing another ID.

Use WordPress tool failed if the plugin rejects the read. Keep the workflow read only while investigating.

Continue with Access modes before allowing changes.