Skip to main content
Glama

delete_post

DestructiveIdempotent

Delete a WordPress post or page by ID, with optional permanent force deletion that bypasses the trash.

Instructions

Delete a WordPress post or page

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": {
      "post_id": "<post_id>"
    },
    "name": "delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce delete (bypass trash, permanently delete)
post_idYesPost or page ID to delete
post_typeNoContent type being deleted. Defaults to 'post'.post

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.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, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds only the resource scope and says nothing about whether deletion is recoverable via trash, what happens on a missing ID, or what deleting a page with children does.

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?

A single front-loaded sentence with zero filler. It is efficient but so terse that the deletion semantics are left entirely to the schema and annotations.

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 mutation with no output schema, the definition omits recovery semantics (trash vs force), permission requirements, and what the caller gets back on success or failure. The annotations carry the safety signal, but the description does too little for a delete operation.

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%, with force, post_id, and post_type all documented including the enum. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

"Delete a WordPress post or page" gives a specific verb and resource, and the resource scope ('post or page') distinguishes it from delete_category, delete_tag, and delete_media. It does not explicitly name an alternative or clarify the trash-vs-permanent distinction, but the core action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. The description never explains that the default behavior is likely trashing versus permanent deletion, or when an agent should reach for this instead of a bulk/media cleanup sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.