mcp-wordpress

wp_seo_set_meta

Write SEO meta for a WordPress post: title, description, Open Graph, Twitter Card, canonical, robots, JSON-LD article, and focus keyword. Works with the active provider, ignoring unsupported fields.

Instructions

Write SEO meta for a post via the active provider. Pass any subset of: title, description, og_title, og_description, og_image (URL), og_type, twitter_card, canonical (URL), robots ({noindex,nofollow,noarchive,nosnippet,noimageindex}), json_ld_article (object), focus_keyword. Fields not supported by the active provider are silently ignored — call wp_seo_detect_provider to know which features apply.

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": {
      "post_id": "<post_id>",
      "meta": "<meta>"
    },
    "name": "wp_seo_set_meta"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	Yes
`post_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses partial updates ('Pass any subset'), silent ignoring of unsupported fields, and points to provider detection. However, it doesn't mention whether existing meta is overwritten or merged beyond the subset implication, and no return behavior is specified.

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?

Two concise sentences: the first states the core action, the second lists all supported fields and the critical caveat. No wasted words, and the structure is front-loaded with the purpose.

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 write tool with no output schema, the description covers the essential behaviors: what fields are accepted, that partial updates are possible, and that unsupported fields are ignored. It also references the provider detection tool. Missing details like return format or auth requirements are not critical given the context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description compensates by enumerating all accepted meta fields, adding format hints (URL, object, robots structure), and clarifying that a subset is allowed. This adds meaning beyond the raw schema.

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 the verb 'Write' and resource 'SEO meta for a post', distinguishing it from the sibling getter wp_seo_get_meta. It also specifies 'via the active provider', which is a unique qualifier.

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

Usage Guidelines5/5

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

The description explicitly tells the agent to call wp_seo_detect_provider to know which features apply, and warns that unsupported fields are silently ignored. This is clear guidance on when to use this tool and which alternative to consult first.

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

Deploy Server