Opus Growth

Inspect WordPress Page Design

Inspect how a WordPress page is actually built (Elementor, WPBakery, Gutenberg, classic) and read its editable design fields.

Type
Lecture seule
Crédits
1
Plateforme
WordPress
Validation
Inutile, rien ne change

Ce qu'il fait

Inspect how a WordPress page is actually built (Elementor, WPBakery, Gutenberg, classic) and read its editable design fields.

It returns the page's element tree, which wordpress_edit_page_design addresses. On an Elementor page the visible design lives in page-builder data, not in the post content, so a plain content update changes nothing. This returns each element's id and the text, links and settings you can change. Pass `element` (an id from the list) to get that one element's full settings, including colours, typography and spacing.

La description est en anglais car c'est le texte officiel que voit votre IA.

MCP: wordpress_page_design

Comment l'utiliser

Vous n'appelez pas les outils par leur nom. Écrivez ce que vous voulez dans ChatGPT, Claude ou un autre assistant connecté à Opus Growth ; l'IA choisit cet outil quand il convient.

Paramètres

NomTypeObligatoirePar défaut
idintegerObligatoire·Exact resource identifier to target. Prefer an ID returned by an Opus Growth list or create operation.
elementstringFacultatif·Exact page-builder element selector or identifier to edit, returned by the relevant page inspection operation; do not use a visual label when an identifier is available.
offsetintegerFacultatif0Zero-based position at which to start reading results. Use the next_offset returned by the previous response when present.
limitintegerFacultatif60Maximum number of rows returned in this response. When the result has_more flag is true, continue with next_page_token rather than assuming the list is complete.
site_urlstringFacultatif·Exact URL of the connected WordPress site to target when more than one site is available.