AutoWP MCP Server

bulk-update-posts

Apply status, author, category, and tag changes to multiple WordPress posts at once.

Instructions

Batch edit multiple WordPress posts

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postIds": "<postIds>",
      "updates": "<updates>"
    },
    "name": "bulk-update-posts"
  }
}

Input Schema

Name	Required	Description	Default
`postIds`	Yes	Array of post IDs to update
`updates`	Yes	Updates to apply to all selected posts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

C2.6/5.0

Behavior1/5

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It does not disclose whether updates replace existing values, whether the operation is destructive, requires authentication, or has any side effects. For a bulk mutation tool, this is a critical omission.

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

Conciseness4/5

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

The description is a single sentence with no fluff, making it concise and front-loaded. However, it is under-specified, sacrificing necessary detail for brevity, but it still earns a high score for conciseness.

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

Completeness1/5

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

For a bulk edit tool with no output schema and a nested updates object, this description is woefully incomplete. It fails to mention the scope of updates, behavior on partial failures, relationship to other content operations, or any constraints. The description gives an agent almost no context to use the tool correctly.

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?

The input schema covers 100% of parameters with descriptions for postIds and updates, so the schema does the heavy lifting. The description adds no extra parameter semantics beyond what is already in the schema, resulting in a baseline score.

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

Purpose4/5

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

The description 'Batch edit multiple WordPress posts' clearly indicates the tool operates on multiple posts, distinguishing it from single-post tools like update-post. The verb 'edit' is a bit generic but combined with 'batch' and 'multiple' makes the purpose clear.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool vs alternatives like update-post or assign-categories-to-posts. The description only implies multiple posts via 'batch' and 'multiple', but does not explicitly state that it is the preferred choice for bulk operations or when to avoid it.

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