WordPress MCP tools, searchable by name.

How GoBuildWP's MCP tool names are built

Every name follows the same pattern: the wppilot/ namespace, the module, then a verb and an object, as in wppilot/bricks-get-global-class or wppilot/woocommerce-list-orders. Core WordPress abilities skip the module part, so creating a post is wppilot/create-post. Once you know the pattern, searching this list by plugin name and verb finds almost anything.

The verbs carry meaning, and it is worth knowing them before you approve a call.

• check-setup: the first call in almost every module. It reports the plugin's version against GoBuildWP's minimum, the edition, and what is available on this install.
• list and get: reads. list returns compact rows to choose from; get returns one object in full.
• Schema reads such as elementor-get-schema or flatsome-get-element-schema: the exact settings a plugin accepts, so the agent writes real keys instead of guessing.
• edit and update: change named fields and leave the rest as they were.
• set-content and set-layout: replace a whole stored structure. In the builder modules these are marked destructive, so they need confirmation.
• delete: removes something. Some deletes move to the trash by default and need force to be permanent; read the ability's own description.
• preview, dry_run and confirm: the parameters and companion abilities that let you see a change before it is made.

Common jobs and the abilities that do them

• Edit text in an Elementor section: elementor-find-elements, then elementor-edit-element (Free).
• Fix SEO titles across many posts: seo-bulk-get-meta, then seo-bulk-update-meta, up to 100 posts per call, through whichever SEO plugin is active (Pro).
• Add alt text to images: audit-media-alt, then update-image-alt (Free).
• Refund part of an order: woocommerce-get-order, then woocommerce-create-refund, which needs confirmation (Pro).
• Replace a phone number everywhere: search-replace-preview, then search-replace-apply (Free).
• Find out why a page is slow: cache-check-setup and cache-measure-page (Pro), or performance-audit (Free).
• See what an agent changed and undo it: list-changes, get-change, rollback-change (Free).

Reading an ability's annotations before you approve it

Each entry in the reference carries two flags from the plugin source: read-only and destructive. Read-only abilities are the only ones the Read Only profile lets through. Destructive marks an operation whose effect is hard to take back, such as deleting, replacing a whole layout or issuing a refund, and those usually need confirm=true. Neither flag tells you whether a change can be undone afterwards; that depends on whether the write records a before-image, and the change list says so per entry. When a client asks you to approve a call, the ability name plus those two flags tell you most of what you need to decide.

Keeping the tool list small for your client

A large site with Pro active can expose hundreds of abilities, and some AI clients handle a long tool list worse than a short one: more tokens spent on definitions, and more chances to pick a near-miss. There are three ways to narrow what a connection sees. Switch off whole abilities you never use on the GoBuildWP Abilities screen. Give each workflow its own access token limited to named abilities or categories, so an SEO agent sees SEO tools and nothing else. And use the Read Only profile for any connection that only needs to look, which removes every write from discovery at once.

Where Free and Pro both register an ability under the same name, there is only ever one tool: with Pro active, Pro's fuller copy registers first and answers for that name. That is why the counts above deduplicate shared names.