GenerateBlocks
These abilities register when GenerateBlocks is detected on the site and a Pro licence is active. If either is missing the module stays absent rather than failing at call time.
At a glance
GenerateBlocks registers 3 abilities: 3 that only read, 0 that write, and 0 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
What this module is for
Discover GenerateBlocks blocks and retrieve their schemas so an AI client can prepare valid Gutenberg changes through WPPilot's staged content workflow.
Before you rely on it: Finalize and visually inspect generated blocks in WordPress before publishing.
Typical workflows
- Discover available blocks before drafting a layout
- Validate attributes against the block schema
- Stage a multi-block change for browser finalization
The GenerateBlocks integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.
Availability on your site
The GenerateBlocks module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/generateblocks-check-setupCheck GenerateBlocks Setup | Reports the presence + version of GenerateBlocks (free) and GenerateBlocks Pro, plus the count of blocks registered under each namespace. This integration is an introspection layer ONLY — it does NOT read or write post_content. To read or write block trees on a post, use the wppilot/gutenberg-* abilities exposed by the base WPPilot plugin (gutenberg-get-content, gutenberg-add-pending-change, gutenberg-enable-batch-finalization, …). Use this check-setup at the start of any session that will compose GenerateBlocks block_spec payloads before submitting them via gutenberg-add-pending-change. |
wppilot/generateblocks-get-block-schemaGet GenerateBlocks Block Schema | Returns the full attribute schema, nesting constraints, and supports map for a single GenerateBlocks-family block. Attributes come straight from WP_Block_Type::$attributes — each key carries type, default, enum when relevant, and any other JSON Schema fields the block author declared. parent / ancestor are nesting constraints (the block can only live inside one of these). uses_context lists the block-context keys this block reads from its ancestors (e.g. a loop-item reads the query context). Pair this with generateblocks-list-blocks (catalogue lookup) and wppilot/gutenberg-add-pending-change (write path). |
wppilot/generateblocks-list-blocksList GenerateBlocks Blocks | Lists every block currently registered in the generateblocks/* (free) or generateblocks-pro/* (Pro) namespace as a compact catalogue: name, title, family, category, is_dynamic, attribute count, and parent/ancestor nesting hints. Use this to browse the available blocks before calling generateblocks-get-block-schema for the full attribute schema of a specific block. Output is deliberately lean (no attribute schemas) — call get-block-schema only on the block you intend to author. |