Skip to main content
Glama

royal-mcp__wp_audit_seo_bulk

Read-onlyIdempotent

[Royal MCP Pro] Generic on-page SEO audit across a post type — checks the basics (title/description length, noindex, H1 count, word count, images + alt-text, featured image). Uses the active SEO plugin as the source of title + meta description when one is detected (Yoast, Rank Math, SEOPress, AIOSEO, or SEObolt); falls back to WordPress-native fields (post_title, post_excerpt) otherwise. Does not surface plugin-native scores (e.g. SEObolt geo_score, Yoast readability). Returns per-page findings + optional aggregated rollup (issues by type, worst offenders). Publish-only by default; pass include_drafts=true for pre-publish workflow audits. The content is read as stored and nothing in it is run (no shortcodes, blocks or embeds), so text and images a shortcode or dynamic block adds when the page is served are not counted; such pages are marked content_made_when_served. Title and description text is sent back up to 300 characters with its full length. A call stops after about 20 seconds or about 1 MB of findings… Through Royally: read-only, runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "royal-mcp__wp_audit_seo_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
rollupNoInclude the aggregated rollup summary alongside per-page results. Default: true.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
paginateNoPagination controls. Defaults: page 1, per_page 100 (max 500).
post_idsNoOptional. When provided, audit ONLY these post IDs (must be of post_type; a list of 1 to 500 whole numbers, anything else is refused). Results come in ID order, paged by paginate. Skips the pagination sweep of every post — useful for targeted re-audit after a fix, or for auditing a specific customer complaint.
snapshotNoAccepted for compatibility; no backup is taken. The audit only reads, so it needs none — sitevault_snapshot reports status "skipped". To back up before a bulk write, call sv_create_backup first.
post_typeNoPost type to audit (must be a registered CPT slug). Default: "post".
include_draftsNoInclude draft/pending/private/future posts alongside published ones. Default: false (publish-only). Agents auditing an SEO surface typically care about what customers actually see, so drafts are opt-in.
verify_rendered_h1NoWhen the theme renders the post title outside the content, load the served page to count its visible H1s instead of reporting h1_unverifiable_theme_title. This loads up to 10 published pages per call the way a visitor gets them, which runs the site's normal page code (theme, plugins, shortcodes) for those pages; each load counts against the per-page limit the page tools share. Adds h1_rendered_count. Default: true; pass false to only read stored data.
count_decorative_altsNoHow to treat alt="" (HTML5 decorative-image marker). Default: true — counts decorative images in images_missing_alt + flags "N_images_missing_alt" issue (strict SEO parity, matches agency-audit convention). Set false to only count images with NO alt attribute at all — separates decoration from missing metadata. images_no_alt + images_decorative_alt are always returned separately regardless of this setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / post_ids / description
      Previous value: -"Optional. When provided, audit ONLY these post IDs (must be of post_type). Skips the pagination sweep of every post — useful for targeted re-audit after a fix, or for auditing a specific customer complaint."New value: +"Optional. When provided, audit ONLY these post IDs (must be of post_type; a list of 1 to 500 whole numbers, anything else is refused). Results come in ID order, paged by paginate. Skips the pagination sweep of every post — useful for targeted re-audit after a fix, or for auditing a specific customer complaint."
    • changedInput schema / properties / verify_rendered_h1 / description
      Previous value: -"When the theme renders the post title outside the content, load the served page to count its visible H1s (up to 10 pages per call) instead of reporting h1_unverifiable_theme_title. Adds h1_rendered_count. Default: true."New value: +"When the theme renders the post title outside the content, load the served page to count its visible H1s instead of reporting h1_unverifiable_theme_title. This loads up to 10 published pages per call the way a visitor gets them, which runs the site's normal page code (theme, plugins, shortcodes) for those pages; each load counts against the per-page limit the page tools share. Adds h1_rendered_count. Default: true; pass false to only read stored data."
  2. Added
  3. Removed
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent, but the description adds substantial non-obvious behavior: content is read as stored so shortcode/dynamic-block output is not counted (flagged content_made_when_served), calls stop at ~20s or ~1MB, returned title/description text is capped at 300 chars, and no backup is taken despite snapshot being accepted. It also discloses that verify_rendered_h1 actually loads up to 10 published pages and runs theme/plugin code, which is a materially important side effect.

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?

Purpose and the check list are front-loaded, and most sentences carry operational information. It is dense but long, and a few clauses (the full SEO plugin name list, the snapshot-compatibility aside, the closing 'Through Royally' tag) are lower-value than the surrounding content.

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 9-parameter, no-output-schema audit tool, it covers the essentials: what findings and rollup are produced, some concrete issue/field names (h1_unverifiable_theme_title, images_no_alt, h1_rendered_count), and truncation/time limits. It stops short of enumerating the full finding schema or all issue types, which an agent would otherwise have to discover empirically.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining intent behind parameters — why drafts are opt-in, why post_ids is useful and that results come in ID order, and the strict-SEO-parity rationale for count_decorative_alts defaulting to true. It does not add much beyond the schema for post_type or paginate, keeping it from a 5.

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?

States a specific verb and resource ('on-page SEO audit across a post type') and enumerates the exact checks performed (title/description length, noindex, H1 count, word count, images + alt-text, featured image). It also explicitly delimits scope against adjacent concepts by saying it does not surface plugin-native scores like SEObolt geo_score or Yoast readability.

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?

Gives clear context for the two main modes: publish-only by default for what customers see, include_drafts=true for pre-publish workflow audits, and post_ids for targeted re-audit after a fix or a specific complaint. It does not name sibling tools such as wp_audit_agent_readiness or seo_audit_meta_tags as alternatives, so routing between audit tools is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources