Skip to main content
Glama

royal-mcp__wp_delete_post

Destructive

Delete a post of any post type. Without force it moves to the trash and can be undone; if the post cannot be trashed (already in the trash, or the site has the trash turned off) the call is refused and nothing is deleted. force: true deletes permanently. A custom_css post needs what wp_update_custom_css needs; refusal codes insufficient_caps, unfiltered_html_required, theme_writes_off. (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

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": "royal-mcp__wp_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
forceNoSkip the trash and delete permanently
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the default path is reversible, that non-force deletion fails closed rather than falling back to permanent delete, the specific refusal codes (insufficient_caps, unfiltered_html_required, theme_writes_off), custom_css prerequisites, and the Royally human-approval gate that blocks any site change until a person approves. That is exactly the pre-call behavioral context a destructive tool needs.

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?

Front-loads the action and the default-vs-force split, then layers refusal codes and the approval gate, so nothing critical is buried. Minor waste: the '(site: demo.royalplugins.com)' annotation duplicates the enum description in the schema, and 'needs what wp_update_custom_css needs' is a vague pointer the reader must chase down.

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, approval-gated mutation with no output schema, the description covers reversibility, permanent-delete semantics, refusal conditions, prerequisites, and the pending-approval outcome. It omits what a call returns (e.g., a deleted/trashed status object or an execution receipt) and whether associated meta, terms, or revisions are affected.

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 67% and the description meaningfully extends the terse schema text for force by explaining the consequence of not setting it and the failure mode when trashing is impossible. The id parameter is never explained beyond the name, and the custom_css prerequisite chain is referenced by analogy rather than spelled out.

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?

States a specific verb and resource ('Delete a post') plus an explicit scope ('of any post type'), which lets an agent know it generalizes across types. It does not address the sibling wp_delete_page, which overlaps since pages are a post type, leaving the agent to guess which one is preferred.

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 operational guidance: default is trash-and-undoable, force:true is permanent, and the call is refused when trash is unavailable (already trashed or trash disabled). It lacks explicit routing to alternatives such as wp_delete_page or a restore/undo sibling, so it stops just short of full when/when-not guidance.

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