Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Delete page

wordpress_delete_page
Destructive

Delete a WordPress page permanently or move it to the trash by providing the site and page ID.

Instructions

[UNIFIED] Delete or trash a WordPress page. Can permanently delete or move to trash.

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": {
      "site": "<site>",
      "page_id": "<page_id>"
    },
    "name": "wordpress_delete_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
forceNo
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is covered structurally. The description adds genuine value by disclosing that deletion may be recoverable via trash, but it omits which mode is the default, whether a trashed page can be restored, and what permissions are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the second sentence ('Can permanently delete or move to trash') is essentially a restatement of the first sentence rather than new information. The space would have been better spent on parameter behavior.

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

Completeness2/5

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

This is a destructive three-parameter tool with zero schema description coverage and no output schema. The description explains the general effect but not the mechanism (which argument makes the deletion permanent) nor the result, so an agent cannot call it correctly from this text alone.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and does not. Neither 'site', 'page_id', nor 'force' is named or explained; the binary trash/permanent behavior is hinted at but never tied to the force flag or its false default, leaving the most consequential parameter undocumented.

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 pairs a specific verb ('delete') with a specific resource ('WordPress page') and adds the trash-vs-permanent distinction. It is clearly separable from the create/get/update page siblings, though it never names them.

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 implies two modes of operation ('permanently delete or move to trash') but never states when each applies or which input selects which mode. An agent must guess that the force flag controls the choice, and there is no warning about prerequisites or exclusions.

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