wordpress_set_seo_metaSet SEO metadata for a WordPress post by providing its ID, compatible with Yoast SEO, Rank Math, and All-in-One SEO plugins.
Set SEO metadata (Yoast SEO, Rank Math, All-in-One SEO compatible)
| Name | Required | Description | Default |
|---|---|---|---|
| postId | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It mentions compatibility but does not state whether existing SEO meta is overwritten, what happens if no SEO plugin is active, or the exact side effects. The write nature is implied but not elaborated.
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 sentence, but it is under-specified rather than appropriately concise. It omits essential details that would require additional sentences or structured information, so the brevity is not a virtue here.
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 minimal schema, no output schema, and no annotations, the description is severely incomplete. It fails to explain the metadata structure, how values are passed, plugin-specific behavior, or any return value, making the tool unsafe and impossible to invoke correctly.
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?
The schema provides only a postId parameter with 0% description coverage, and the description adds no meaning about how SEO metadata values are supplied or what postId refers to. The agent cannot infer any parameter behavior beyond the name, making the tool unusable without additional context.
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 identifies the action ('Set SEO metadata') and specifies compatibility with common SEO plugins, which conveys the general purpose. However, it does not detail what specific metadata fields are affected or distinguish this tool from siblings like set_og_tags or set_twitter_cards, leaving the scope ambiguous.
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 provided on when to use this tool versus alternatives such as set_custom_meta, set_og_tags, or set_canonical_url. There is no mention of prerequisites, plugin requirements, or situations where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.