mcp-wordpress

wp_pages_delete

Delete a WordPress page, sending it to trash by default. Optionally force permanent deletion with confirmation; child pages are orphaned.

Instructions

Delete a page. Default sends it to the trash (recoverable). Pass force=true with confirm="DELETE_PERMANENTLY_" to permanently delete (requires MODE=full). Deleting a parent page with children: WP behavior is to orphan children (their parent becomes 0); the MCP does not auto-cascade.

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": {
      "id": "<id>"
    },
    "name": "wp_pages_delete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`force`	No
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility and does so thoroughly. It reveals dangerous/irreversible behavior (permanent delete requires explicit confirm), prerequisites (MODE=full), and a non-obvious edge case (children are orphaned, no auto-cascade). This exceeds the bare minimum and gives strong transparency.

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?

Four concise sentences, front-loaded with the core action ('Delete a page') followed by necessary exceptions and edge-case behavior. Every sentence provides practical information without fluff or repetition.

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 destructive operation with no annotations and no output schema, the description covers safety, prerequisites, and an important edge case. It does not describe the return value or error handling, which would arguably be useful in the absence of an output schema, but the operational guidance is strong enough to be nearly complete.

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

Parameters5/5

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

Schema coverage is 0% because property descriptions are absent, so the description must compensate. It explains the exact confirm format ('DELETE_PERMANENTLY_<id>'), when force is required, and implies id is the page to delete. This adds significant semantic value beyond the schema.

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?

Clearly states 'Delete a page' with specific verb and resource. The description distinguishes this tool from sibling delete tools (posts, media, CPTs) by naming 'page' and details trash vs. permanent deletion, which uniquely identifies its purpose.

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?

Provides clear context: default sends to trash (recoverable), permanent deletion requires force=true plus a specific confirm string and MODE=full. It also explains parent-child cascade behavior, but does not explicitly mention alternatives or when to use a different delete tool (e.g., posts vs. pages), 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