wpxmcp

Bulk update content

bulk_update_content

Update many posts in one batch: set status, reassign author, add categories/tags, or find/replace within bodies. Preview shows affected items first; confirm with token to apply.

Instructions

Apply the same change to many items at once — set a status, reassign an author, add a category, or run a find/replace across bodies. Always previews first: the initial call reports exactly which items would change and how, and returns a confirm_token you must echo back to apply it. Nothing is written without that token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Content type to operate on.	post
`limit`	No	Hard ceiling on how many items can be touched in one call.
`filter`	No	Which items to act on. Without any filter this would match everything, so a limit always applies.
`changes`	No	Field changes applied to every matched item.
`site_id`	No	Which configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
`confirm_token`	No	Token from the preview. Required to actually write.
`content_edits`	No	Find/replace applied to each item's body. Items where nothing matches are skipped rather than failing the batch.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedv2.0.0Sep 15, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / changes / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / changes / properties / add_categories / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / changes / properties / add_categories / items / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / changes / properties / add_tags / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / changes / properties / add_tags / items / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / changes / properties / author / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / changes / properties / author / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / changes / properties / meta / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / changes / properties / remove_categories / description
```
Added value: +"Category IDs to detach."
```
- addedInput schema / properties / changes / properties / remove_categories / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / changes / properties / remove_categories / items / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / changes / properties / remove_tags
```
Added value: +{
+  "description": "Tag IDs to detach.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}
```
- changedInput schema / properties / changes / properties / status / description
```
Previous value: -"Filter by status."New value: +"Set every matched item to this status. \"trash\" moves them to the trash (recoverable)."
```
- changedInput schema / properties / changes / properties / status / enum
```
Previous value: -[
-  "publish",
-  "draft",
-  "pending",
-  "private",
-  "future",
-  "trash"
-]New value: +[
+  "publish",
+  "draft",
+  "pending",
+  "private",
+  "trash"
+]
```
- addedInput schema / properties / changes / properties / template / description
```
Added value: +"Page template file to set, or empty string for the default."
```
- removedInput schema / properties / content_edits / items / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / content_edits / items / properties / all / description
```
Added value: +"Replace every occurrence. Without it, an item where the text appears more than once is skipped as ambiguous."
```
- addedInput schema / properties / content_edits / items / properties / find / description
```
Added value: +"Exact text (or regex with regex: true) to find in each raw body."
```
- addedInput schema / properties / content_edits / items / properties / find / minLength
```
Added value: +1
```
- addedInput schema / properties / content_edits / items / properties / regex / description
```
Added value: +"Treat `find` as a JavaScript regular expression."
```
- addedInput schema / properties / content_edits / items / properties / replace / description
```
Added value: +"Replacement text. Empty string deletes the match."
```
- removedInput schema / properties / filter / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / filter / properties / author / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / filter / properties / author / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / filter / properties / categories / description
```
Added value: +"Only items in any of these category IDs."
```
- addedInput schema / properties / filter / properties / categories / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / filter / properties / categories / items / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / filter / properties / ids / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / filter / properties / ids / items / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / filter / properties / tags / description
```
Added value: +"Only items with any of these tag IDs."
```
- addedInput schema / properties / filter / properties / tags / items / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / filter / properties / tags / items / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.0Aug 24, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

It discloses a critical two-step behavior: the initial call returns a confirm_token and nothing is written without it. This goes beyond the annotations (readOnlyHint=false, destructiveHint=false) by explaining the actual write gate. It also notes that items with no matches are skipped, which is useful context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose and then the critical preview/confirm requirement. No filler or redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 params, nested objects, no output schema), the description covers the essential flow (preview → confirm token → apply) and mentions skipping non-matching items. It does not describe the return format, but since no output schema exists, the description could have said more; however, the critical usage constraints are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description provides a high-level summary of the change types (status, author, category, find/replace) but does not add specific parameter details beyond what the schema already documents. It adds no new semantic meaning for parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: applying the same change to many items at once, and enumerates concrete operations (set status, reassign author, add category, find/replace). It distinguishes itself from single-item tools like update_content by emphasizing 'many items at once'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case (bulk vs. single) and explicitly outlines the required preview-confirm flow. However, it does not name alternative tools for single-item edits or state when not to use it, though the context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Bulk update content

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools