Skip to main content
Glama

royal-mcp__wp_prepare_for_launch

Destructive

[Royal MCP Pro] Site-readiness rollup: SEO audit (SEObolt or native), broken-link scan of home-page same-origin refs (up to 25, about 15 seconds in all; checked / stopped_early say how many were probed), TTFB perf check, security status (GuardPress or native). Read-only unless backup=true, which first queues a SiteVault backup (skipped while another backup is running). Default compose_mode=best_effort — every step runs independently. No undo. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.

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_prepare_for_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
backupNoIf true, queue a SiteVault backup before the checks. Default false. Skipped while another backup is running.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
skip_backupNoDeprecated — the backup is off unless backup=true. Still honoured: true always skips it.
compose_modeNostrict aborts + rolls back on first error; best_effort continues past failures; report_only returns the plan for write sub-ops AND executes read-only sub-ops (audit / schema-verify) so callers get real findings from a dry-run. Write sub-ops never mutate in report_only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses concrete behavior: link probing is capped at 25 refs (~15s), checked/stopped_early report how many were probed, the SiteVault backup is skipped while another is running, there is no undo, and the call blocks on human approval before anything changes. That is real operational context an agent could not derive from readOnlyHint=false/destructiveHint=true alone. It still leaves the overall result payload shape vague.

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 is front-loaded and no sentence is filler — timing, caps, backup skipping, and approval gating all carry information. The density of parentheticals (SEObolt or native, checked / stopped_early, the site URL) makes it slightly harder to scan than it needs to be.

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 multi-step audit with no output schema, the definition covers the important ground: what runs, limits, timing, failure modes via compose_mode, and the approval gate. It never sketches the rollup's result structure beyond two named fields, so an agent cannot anticipate what a full report looks like.

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 carries the semantics of backup, skip_backup, site_id, and the three compose_mode values. The description adds only marginal value, chiefly the statement that best_effort is the default and that steps run independently. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names the resource precisely — a site-readiness rollup — and enumerates its constituent steps (SEO audit via SEObolt or native, broken-link scan, TTFB perf, security status via GuardPress or native). An agent can tell this is a composite audit rather than a single-check tool. It stops short of naming which sibling it replaces (e.g. wp_audit_seo_bulk or seo_optimize_for_launch), so differentiation is inferred rather than stated.

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?

It gives useful operating context: default compose_mode=best_effort with every step running independently, backup=false by default, and a note that the call is gated by human approval in Royally. However, it never says when an agent should pick this rollup over the narrower audit siblings, nor when the backup path is warranted beyond the parameter's own description.

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