Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_get_page_seo

Retrieve SEO metadata for any WordPress page or post using All in One SEO, including title, description, and schema, to audit and optimize search visibility.

Instructions

Get SEO metadata for a page/post via All in One SEO (title, description, schema, etc.)

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": {
      "page_id": "<page_id>"
    },
    "name": "wp_get_page_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesWordPress page or post ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It accurately indicates a read operation ('Get') and names the data source ('All in One SEO'), but does not disclose behaviors such as what happens when the plugin is missing, error conditions, or the exact shape of the returned metadata beyond examples.

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?

The description is a single sentence with no filler. It front-loads the action and resource, then lists representative return fields. The 'etc.' is minor and does not detract from the overall efficiency.

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 simple getter with one well-documented parameter and no output schema, the description provides enough context: what is fetched, the source, and example output fields. It could be more complete by noting plugin dependency or error handling, but those are not critical for basic invocation.

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 100%, with page_id described as 'WordPress page or post ID'. The description's mention of 'page/post' adds a small clarification that page_id may refer to either type, but it does not provide meaning beyond what the schema already states.

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 ('Get') and resource ('SEO metadata for a page/post via All in One SEO'), with concrete examples of what is included. This clearly distinguishes it from sibling tools like wp_get_page (general page data) and wp_update_page_seo (write operation).

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 description implies when to use the tool: when you need SEO metadata for a single page or post. However, it does not explicitly mention alternatives or scenarios where wp_audit_seo or wp_get_page would be more appropriate, so usage guidance is only implicit.

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