Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Delete post

wordpress_delete_post
Destructive

Delete or trash a WordPress post by site and post ID; choose permanent deletion or move it to trash.

Instructions

[UNIFIED] Delete or trash a WordPress post. 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>",
      "post_id": "<post_id>"
    },
    "name": "wordpress_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
forceNo
post_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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description adds only that a trash mode exists; it does not say that omitted `force` defaults to trashing, whether trashed posts are recoverable, or what happens on a nonexistent post_id. For a destructive mutation with 0% schema coverage, that is a meaningful gap.

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?

Two short sentences, outcome-first, with no wasted clauses. Slight redundancy in restating 'delete or trash' twice, but it is tight overall.

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?

For a destructive, non-idempotent mutation with three undocumented parameters and no output schema, an agent cannot determine how to invoke permanent deletion versus trashing. The definition is missing the one piece of information the schema does not supply: the meaning of `force`.

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% and none of the three parameters are documented. The description alludes to a trash-vs-permanent distinction but never names `force`, its default, or its effect, and gives no hint about what `site` expects (slug, URL, ID). The description therefore fails to compensate for the schema gap.

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 or trash a WordPress post') and names the two possible outcomes, which separates it from the create/get/update post siblings. It does not explicitly disambiguate from wordpress_delete_page or other delete tools, so it falls short of a 5.

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?

The description conveys that there are two modes (permanent delete vs. move to trash) but never says when to prefer one, and never connects these modes to the `force` parameter or mentions irreversibility/recovery. No alternatives or prerequisites are named.

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