mcp-wordpress

wp_bulk_update_seo

Apply the same SEO metadata to multiple WordPress posts at once. Preview via dry-run, then confirm with token to write changes through your SEO provider.

Instructions

Apply the same SEO meta to many posts at once. Requires MODE=full. Dry-run by default (returns count + sample). To apply, set dry_run=false with the confirm token from dry-run. Writes via the active SEO provider — fields unsupported by the provider are silently dropped.

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": {
      "filter": "<filter>",
      "meta": "<meta>"
    },
    "name": "wp_bulk_update_seo"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	Yes
`filter`	Yes
`confirm`	No
`dry_run`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the responsibility of disclosing behavior. It reveals that the tool is write-oriented, safe by default (dry-run), requires a confirmation token, writes through the active SEO provider, and silently drops unsupported fields. This is substantial and non-obvious behavioral 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?

The description is four sentences, each adding necessary information: purpose, mode requirement, dry-run default, apply workflow, and provider behavior. There is no filler, repetition, or unnecessary detail.

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?

For a complex bulk-update tool with no output schema, the description covers the main workflow, safety mechanism, and provider caveat. It notes the dry-run return type (count + sample) but does not describe exact response formatting or batching/pagination behavior, which are relevant for a tool with a per_page parameter.

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 0%, so the description must compensate. It does explain dry_run, confirm, and the general semantics of meta, but filter and per_page are not described beyond their schema names and types. This leaves a moderate gap for parameters that are central to selecting which posts are updated.

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 opens with a specific verb and object — 'Apply the same SEO meta to many posts at once' — which clearly conveys the tool's bulk update purpose. This distinguishes it from single-post SEO tools like wp_seo_set_meta and from other bulk operations like wp_bulk_find_replace.

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 gives explicit usage instructions: requires MODE=full, dry-run by default, and the exact steps to apply changes using dry_run=false with the confirm token. It does not explicitly name alternatives for single-post updates, but the bulk phrasing makes the intended use clear.

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

Deploy Server