@respira/wordpress-mcp-server 8.3.21 → 8.3.23

package/dist/server.js

@@ -18,6 +18,7 @@ import { getBricksTools, dispatchBricksTool } from './bricks-tools.js';
 import { getElementorTools, dispatchElementorTool } from './elementor-tools.js';
 import { getAcfTools, resolveAcfToolName } from './acf-tools.js';
 import { getUsageEmitter, deriveToolKind } from './usage-emitter.js';
+import { FSE_OPERATION_ITEM_SCHEMA } from './fse-operation-schema.js';
 import { collapseLauncherProcesses, validateApiKeyShape, describeConfigOrigin, configOriginKey } from './config.js';
 // Process-local secret keeps target hashes useful for same-session retry
 // detection without making low-entropy WordPress ids reversible centrally.
@@ -3713,7 +3714,7 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
                         id: { type: 'string' },
                         kind: { type: 'string', enum: ['template', 'template_part'] },
                         expected_fingerprint: { type: 'string' },
-                        operations: { type: 'array', items: { type: 'object' }, maxItems: 50 },
+                        operations: { type: 'array', items: FSE_OPERATION_ITEM_SCHEMA, maxItems: 50 },
                         verification_marker: { type: 'string' },
                         dry_run: { type: 'boolean' },
                         edit_target: { type: 'string', enum: ['approval', 'live'] },
@@ -3824,7 +3825,7 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
                     properties: {
                         id: { type: 'string' },
                         expected_fingerprint: { type: 'string' },
-                        operations: { type: 'array', items: { type: 'object' }, maxItems: 50 },
+                        operations: { type: 'array', items: FSE_OPERATION_ITEM_SCHEMA, maxItems: 50 },
                         verification_marker: { type: 'string' },
                         dry_run: { type: 'boolean' },
                         edit_target: { type: 'string', enum: ['approval', 'live'] },
@@ -3940,7 +3941,7 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
                     properties: {
                         id: { type: 'string' },
                         expected_fingerprint: { type: 'string' },
-                        operations: { type: 'array', items: { type: 'object' }, maxItems: 50 },
+                        operations: { type: 'array', items: FSE_OPERATION_ITEM_SCHEMA, maxItems: 50 },
                         verification_marker: { type: 'string' },
                         dry_run: { type: 'boolean' },
                         edit_target: { type: 'string', enum: ['approval', 'live'] },
@@ -4396,7 +4397,7 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
             },
             {
                 name: 'wordpress_apply_builder_patch',
-                description: 'Apply a list of targeted builder patch operations. Each operation is { identifier: { id|admin_label|path|type [+match_content] }, updates: { content?, attributes?, ...flat_settings? } }. The identifier block follows the same shape as wordpress_find_element\'s identifier; the updates block follows the same shape as wordpress_update_module\'s updates. Returns 400 respira_patch_invalid_operation when an entry is missing either field. This is NOT a JSON-Patch document — do not pass { op, path, value } shapes (those will be rejected). Example: { operations: [{ identifier: { admin_label: "Hero" }, updates: { admin_label: "Hero Content" } }] }.',
+                description: 'Apply a list of targeted builder patch operations. Each operation is { identifier: { id|admin_label|path|type [+match_content] }, updates: { content?, attributes?, ...flat_settings? } }. The identifier is keyed by what you know: { id: "2c3a794b-..." } (a Divi 5 _nodeId, Elementor or Bricks id), { path: "0.2.1" } (the path_string wordpress_find_element returns), { admin_label: "Hero" }, or { type: "divi/text", match_content: "text inside it" }. In the identifier, `type` is the MODULE type, never the kind of identifier. wordpress_find_element\'s vocabulary is also accepted when the value is present: { identifier_type: "id", identifier_value: "..." } and { type: "id", value: "..." } (type one of id, path, admin_label, class, content, text) are read as { id: "..." }. class, content and text resolve only on Divi 4 shortcode pages; elsewhere they are refused with a 400, so look the element up with wordpress_find_element and send its path_string as { path }. An id shared by several elements (duplicated modules keep their id) is refused with respira_patch_ambiguous_target and the candidate paths. The updates block follows the same shape as wordpress_update_module\'s updates. Returns 400 respira_patch_invalid_operation when an entry is missing either field. This is NOT a JSON-Patch document — do not pass { op, path, value } shapes (those will be rejected). Example: { operations: [{ identifier: { admin_label: "Hero" }, updates: { admin_label: "Hero Content" } }] }.',
                 inputSchema: {
                     type: 'object',
                     properties: {
@@ -4421,13 +4422,16 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
                                 properties: {
                                     identifier: {
                                         type: 'object',
-                                        description: 'Element identifier. Provide exactly one of id / admin_label / path / type. match_content disambiguates duplicates of the same type. `path` accepts both dialects: the index form respira_find_element emits ("1.0.1") and the key-interleaved form ("1.children.0.children.1"). They name the same element.',
+                                        description: 'Element identifier. Provide exactly one of id / admin_label / path / type. match_content disambiguates duplicates of the same type. `path` accepts both dialects: the index form respira_find_element emits ("1.0.1") and the key-interleaved form ("1.children.0.children.1"). They name the same element. `type` is the MODULE type ("divi/text"), never the kind of identifier. wordpress_find_element\'s vocabulary is also read: { identifier_type: "id", identifier_value: "..." } or { type: "id", value: "..." } becomes { id: "..." } (type one of id, path, admin_label, class, content, text; value required). Prefer the canonical keys.',
                                         properties: {
-                                            id: { type: 'string', description: 'Builder element ID (Divi 5 _nodeId, Elementor element id, Bricks id, etc).' },
+                                            id: { type: 'string', description: 'Builder element ID (Divi 5 _nodeId, Elementor element id, Bricks id, etc). An id shared by several elements (duplicated modules) is refused with the candidate paths; send one of them as path.' },
                                             admin_label: { type: 'string', description: 'Admin label / navigator label.' },
                                             path: { description: 'Index path as either a dot-string "0.1.2" or an array [0,1,2].' },
-                                            type: { type: 'string', description: 'Module type (e.g. "divi/heading", "et_pb_text", "core/paragraph").' },
+                                            type: { type: 'string', description: 'Module type (e.g. "divi/heading", "et_pb_text", "core/paragraph"). Not the identifier kind: with a `value` next to it, type "id", "path", "admin_label", "class", "content" or "text" is read as find_element vocabulary instead.' },
                                             match_content: { type: 'string', description: 'Optional content substring for disambiguation.' },
+                                            value: { type: 'string', description: 'find_element vocabulary: the value for a `type` of id, path, admin_label, class, content or text. { type: "path", value: "0.2.1" } is read as { path: "0.2.1" }.' },
+                                            identifier_type: { type: 'string', description: 'find_element vocabulary: id, path, admin_label, type, class, content or text. Read together with identifier_value, e.g. { identifier_type: "id", identifier_value: "2c3a794b-..." } is read as { id: "2c3a794b-..." }.' },
+                                            identifier_value: { type: 'string', description: 'find_element vocabulary: the value for identifier_type.' },
                                         },
                                     },
                                     updates: {
@@ -11191,7 +11195,7 @@ Allowlist: css, scss, less, json. PHP / JS theme writes are intentionally out of
                         },
                         options: {
                             type: 'object',
-                            description: 'Conversion options: {status, title, preserve_tokens, font_substitution, responsive}. preserve_tokens (default TRUE): registers the document\'s :root CSS custom properties as the builder\'s own global tokens (Elementor globals, Bricks palette/variables, theme.json, ...) and keeps converted content referencing them, so the design system stays a set of named tokens instead of copied literals. Existing site tokens are never overwritten. Pass preserve_tokens: false to resolve every var() to its literal value and leave the site\'s global stores untouched.',
+                            description: 'Conversion options: {status, title, mode, preserve_tokens, font_substitution, responsive}. mode (plugin 8.8.34+): "fidelity" is the default when the document has a stylesheet on Divi 5 and Bricks: the file\'s structure is kept one to one, every leaf keeps its markup, and the stylesheet travels verbatim scoped to the page, so the page looks like the file and the site\'s design direction is not applied; "restyle" re-types the page in the builder\'s own settings and site tokens. preserve_tokens (default TRUE): registers the document\'s :root CSS custom properties as the builder\'s own global tokens (Elementor globals, Bricks palette/variables, theme.json, ...) and keeps converted content referencing them, so the design system stays a set of named tokens instead of copied literals. Existing site tokens are never overwritten. Pass preserve_tokens: false to resolve every var() to its literal value and leave the site\'s global stores untouched.',
                         },
                     },
                     required: ['html'],