Update SEO meta fields for multiple WordPress posts in a single request, eliminating manual edits per post.
Bulk update SEO meta across multiple posts.
| Name | Required | Description | Default |
|---|---|---|---|
| site | Yes | Site id (see list_sites) | |
| updates | Yes | Bulk update payload (e.g. { posts: [{ id, ...meta }] }) |
Changes observed during successful MCP inspections.
v3.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose mutation side effects, permission requirements, partial-failure behavior, rate limits, or whether existing meta is overwritten. For a bulk write operation, this leaves critical behavior unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a concise summary, though it could carry more useful context without becoming verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is a bulk mutation with a nested 'updates' object, no annotations, and no output schema, the one-line description is not complete enough. It omits prerequisites, expected return behavior, and how to handle multiple posts in a single call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters, including the 'site' reference to list_sites and the 'updates' payload shape. The description adds no additional meaning beyond what the schema provides, making the baseline of 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Bulk update') and resource ('SEO meta across multiple posts'), which distinguishes it from the single-post sibling seo_update_post_seo. It does not explicitly name that sibling or clarify scope boundaries beyond 'bulk', but the purpose is clear and actionable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus seo_update_post_seo, seo_list_posts_seo, or other alternatives. There is no mention of prerequisites, constraints, or conditions that would select this tool over single-post updates.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.