Polylang
These abilities register when Polylang 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
Polylang registers 6 abilities: 4 that only read, 0 that write, and 2 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 Polylang languages and translated content, inspect or assign a post language, and link translations through confirmation-gated WPPilot Pro abilities.
Before you rely on it: The module does not generate translations or manage term translations. Assign each post or page language first, link only matching translated post types, and confirm every assignment or linking write.
Typical workflows
- Audit which posts or pages are assigned to each site language
- Assign a language to existing content after confirming the target
- Link existing same-type translations into a reviewed language set
The Polylang 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 Polylang 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/polylang-check-setupCheck Polylang Setup | Reports the Polylang version, configured languages, default language, translated post types, and relevant administration capabilities. Call this before any Polylang operation. |
wppilot/polylang-get-content-languageGet Content Language and Translations | Reads one post or page language and its complete Polylang translation set. |
wppilot/polylang-list-contentList Polylang Content | Lists translated WordPress content with its assigned language and translation-set summary. Supports post type, language, status, search, and bounded pagination. |
wppilot/polylang-list-languagesList Polylang Languages | Lists the real languages configured in Polylang with slug, locale, W3C code, RTL state, ordering, and default-language state. |
Destructive
Marked destructive in the source, so each call needs an explicit confirmation flag, every time.
| Ability | What it does |
|---|---|
wppilot/polylang-link-content-translationsLink Content Translations | Replaces the Polylang translation mapping for a set of same-post-type content IDs. Every key must be a configured language and every post must already carry that language. |
wppilot/polylang-set-content-languageSet Content Language | Assigns an existing Polylang language to a translated post type. This can detach or alter an existing translation relationship and therefore requires confirmation. |