Skip to main content
Glama
Sign In
MCP WordPress Server

MCP WordPress Server

by docdyhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_seo_bulk_update_metadata

Update SEO metadata for multiple posts at once with built-in progress tracking and error handling to ensure accurate bulk updates.

Instructions

Update SEO metadata for multiple posts with progress tracking and error handling

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": "wp_seo_bulk_update_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite identifier for multi-site setups
dryRunNoPerform a dry run without making actual changes
postIdsYesArray of WordPress post IDs to update
updatesYesMetadata fields to update for all posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.23
  2. Removedv3.3.22
  3. Addedv3.3.8
  4. Removedv3.3.7
  5. Changed4 schema fields changedv3.3.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / updates / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / updates / properties
      Added value: +{
+  "canonical": {
+    "type": "string"
+  },
+  "description": {
+    "type": "string"
+  },
+  "focusKeyword": {
+    "type": "string"
+  },
+  "title": {
+    "type": "string"
+  }
+}
    • removedInput schema / properties / updates / propertyNames
      Removed value: -{
-  "type": "string"
-}
  6. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Mentions progress tracking and error handling, which adds behavioral context beyond the schema. However, no annotations exist, and the description does not disclose mutation details, rollback behavior, or concurrency.

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?

Single sentence that efficiently communicates purpose and key features. No redundancy.

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

Completeness3/5

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

Covers core purpose and mentions progress tracking/error handling, but lacks details on return format, partial updates, or operational behavior given 4 parameters and no output schema.

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 coverage is 100% with good descriptions. The tool description adds no extra parameter meaning beyond what the schema already provides, so baseline score applies.

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 it updates SEO metadata for multiple posts, with progress tracking and error handling. It differentiates from siblings like wp_seo_generate_metadata by focusing on bulk updates.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives like wp_seo_generate_metadata or wp_seo_analyze_content. The bulk nature is implied but not contrasted.

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

Deploy Server

Other Tools