Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get rendered page HTML

get_page_html
Read-only

Fetch server-rendered HTML for any URL on a WordPress site to verify changes actually appear on the front end. Optionally extract SEO head tags or visible text.

Instructions

Fetch the fully rendered HTML that a visitor receives for any URL on the configured site (other hosts, and redirects to them, are refused), so you can verify that a change actually appears on the front end rather than trusting the API's word for it. Returns the server-rendered HTML — content injected later by JavaScript will not appear. Optionally extracts just the SEO-relevant head tags or the visible text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPath or full URL to fetch, e.g. "/about/"./
modeNohtml: the raw markup. text: visible text only. head: title/meta/OG tags. summary: head tags plus headings, links and image alt coverage.summary
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
max_charsNoTruncate the response at this many characters.
preview_tokenNoToken from get_preview_url, to render a draft theme instead of the live one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_chars / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / max_chars / minimum
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses meaningful behavior: only server-rendered HTML is returned, JavaScript-injected content will not appear, other hosts and redirects are refused, and modes can extract head tags or visible text. These limitations materially shape what the caller should expect.

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?

Three sentences, with the core fetch+scoping behavior front-loaded, followed by a crucial rendering caveat and the optional modes. Every sentence carries information and none is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only fetch tool with no required parameters and no output schema, the description covers what is returned (server-rendered HTML), how modes alter the output, and the host/redirect constraint. The input schema completes the remaining parameter details.

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%, so the schema already documents all five parameters, including the mode enum values. The description's mention of optional head/visible-text extraction only paraphrases the mode parameter and adds no new semantics.

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 opens with a specific verb and resource: fetching the fully rendered HTML a visitor receives for any URL on the configured site. It also states the scope restriction (other hosts refused), which distinguishes it from broader fetch-or-search tools in the sibling list.

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

Usage Guidelines4/5

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

It gives a clear use case — verifying that a change actually appears on the front end rather than trusting API data — which is enough to know when to reach for this tool. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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