Skip to main content
Glama

WordPress: Get product seo

wordpress_get_product_seo
Read-only

Retrieve SEO metadata for a WooCommerce product, including Rank Math or Yoast focus keyword, meta title, description, and social settings, to audit or optimize product search visibility.

Instructions

[UNIFIED] Get SEO metadata for a WooCommerce product. Returns Rank Math or Yoast SEO fields including focus keyword, meta title, description, and social media settings. Requires SEO API Bridge plugin.

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": {
      "site": "<site>",
      "product_id": "<product_id>"
    },
    "name": "wordpress_get_product_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's burden is reduced. It adds two useful behavioral facts the annotations don't carry: the dependency on the SEO API Bridge plugin and the fact that output varies by which SEO plugin (Rank Math or Yoast) is installed. It does not say what happens if the plugin is absent or the product has no SEO data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences with the tool's purpose and return shape first and the plugin prerequisite last; no filler. The bracketed [UNIFIED] prefix is noise unless the agent already knows the convention, but it costs little.

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?

For a simple two-parameter read with no output schema, the definition covers purpose, return fields, and the plugin dependency, which is close to adequate. The missing pieces are parameter meaning for 'site' and behavior on missing plugin or empty SEO metadata, which matter because the description itself raises those failure modes.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the schema supplies only types. The description never explains what 'site' identifies (site key, URL, alias?) or that product_id must be a WooCommerce product rather than a variation, so it fails to compensate for the coverage gap.

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 states a specific verb and resource ("Get SEO metadata for a WooCommerce product") and enumerates what comes back (focus keyword, meta title, description, social settings), which distinguishes it from the sibling wordpress_get_post_seo by product-vs-post scope. An agent can tell immediately that this is a read of product SEO fields.

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?

The only usage signal is the prerequisite ("Requires SEO API Bridge plugin"), which is valuable. There is no explicit statement of when to choose this over wordpress_get_post_seo or woocommerce_get_product, nor any when-not guidance, so alternatives are left to inference from names.

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