Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get post seo

wordpress_get_post_seo
Read-only

Retrieves SEO metadata for a WordPress post or page, including focus keyword, meta title, description, and social settings from Rank Math or Yoast via the SEO API Bridge plugin.

Instructions

[UNIFIED] Get SEO metadata for a WordPress post or page. 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>",
      "post_id": "<post_id>"
    },
    "name": "wordpress_get_post_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
post_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

B3.4/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 read, so the bar is lower. The description does add real context beyond annotations: the source plugins (Rank Math or Yoast) and the dependency on the SEO API Bridge plugin, which implies a possible failure mode if it is absent. It does not say what happens when no SEO plugin is active or when a post has no SEO metadata yet.

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 short sentences, front-loaded with the action and followed by return contents and the prerequisite, with no filler. The '[UNIFIED]' prefix is the only non-informative token.

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?

With no output schema, the description must characterize the return value, and it does so at a field-list level, which is adequate for a simple two-parameter read. It is incomplete on two points an agent would want: the response shape when multiple SEO plugins are present and the behavior when SEO metadata is unset or the bridge plugin is missing.

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

Parameters3/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 description must carry the load and largely does not: neither 'site' nor 'post_id' is explained. There is a mild ambiguity worth flagging, since the tool claims to work on 'post or page' but the only identifier is post_id, leaving unstated whether page IDs are accepted there.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get SEO metadata for a WordPress post or page" gives a specific verb and resource, and the second sentence enumerates the concrete fields returned (focus keyword, meta title, description, social settings), which distinguishes it from sibling update tools and from generic post fetchers like wordpress_get_post. It stops short of explicitly naming wordpress_update_post_seo or wordpress_get_product_seo as the contrasting alternatives.

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?

Usage is only implied: an agent can infer this is the read-side counterpart to updating SEO data, but the description never states when to pick this over wordpress_get_post (which may also return SEO block data) or wordpress_get_product_seo for product entities. The one genuinely useful scoping fact, that the SEO API Bridge plugin is required, is stated but framed as a prerequisite rather than a usage condition.

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