Lists SEO meta across posts for a WordPress site so you can review, audit, or filter metadata by post type, search, and page.
List SEO meta across posts.
| Name | Required | Description | Default |
|---|---|---|---|
| site | Yes | Site id (see list_sites) | |
| params | No | Query params (page, per_page, post_type, search, ...) |
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 that this is a read-only operation, whether authentication is required, pagination behavior, or what the response contains. The verb 'List' hints at a safe read, but no explicit traits are described.
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 simple list tool.
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?
For a 2-parameter list tool with a nested params object and no output schema, the description is minimally adequate. It states the core operation but does not clarify return fields, pagination defaults, or how the nested query parameters map to the result, leaving some gaps that the schema alone does not fill.
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 input schema already documents both the required 'site' parameter and the generic 'params' object. The description adds no additional parameter semantics, 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 (List) and resource (SEO meta across posts), which is clear enough to distinguish it from single-post siblings like seo_get_post_seo. However, it does not explicitly name or contrast with those siblings, so it falls short of a 5.
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?
There is no explicit guidance on when to use this tool versus alternatives such as seo_get_post_seo (single post) or seo_bulk_update_posts_seo (bulk update). The plural 'posts' implies a list operation, but no when/when-not conditions or alternatives are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.