Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a content summary

get_content_summary
Read-only

Get a compact summary of any WordPress content item—including SEO fields and word count—without the body, for quick audits and lookups by ID or URL.

Instructions

Return a minimal summary of one item — id, title, slug, status, excerpt, taxonomies, word count and SEO fields (Yoast, Rank Math, AIOSEO or SEOPress) — without the body. Built for audits and lookups over many items. Accepts either an id (with type) or a full URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoContent ID. Provide this or `url`.
urlNoAny front-end URL on the site; the type is detected automatically.
typeNoContent type, used with `id`.post
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.

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 / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already establish read-only and non-destructive behavior. The description adds a concrete return contract by enumerating fields and explicitly excluding the body, which is valuable given the absence of an output schema. It does not detail taxonomy or SEO field shapes, but this is a minor gap for a simple read-only summary.

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 two sentences with the core deliverable and field list front-loaded. Every sentence earns its place, and there is no repetition of schema or annotation details.

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?

With no output schema, the description compensates by listing the exact fields returned and explicitly stating that the body is excluded. Parameter semantics and read-only safety are covered by the schema and annotations, though minor ambiguities remain around taxonomy/SEO field formatting.

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

Parameters4/5

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

The schema already documents all parameters, so the baseline is 3. The description adds cross-parameter meaning by stating that id and url are alternatives and by noting that URL type is detected automatically, which is not explicitly clear in the schema alone. This helps an agent choose the correct invocation.

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 action and resource: return a minimal per-item summary containing a concrete field list (id, title, slug, status, excerpt, taxonomies, word count, SEO fields) without the body. It clearly distinguishes itself from full-content retrieval and bulk listing siblings by emphasizing 'one item' and 'without the body.'

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 says the tool is 'Built for audits and lookups over many items' and clarifies the two accepted input modes (id with type, or a full URL). It does not explicitly name sibling alternatives or state when not to use it, but the context is clear enough for a read-only lookup tool.

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