Skip to main content
Glama

wp_delete_post

Remove a WordPress post to trash or permanent deletion, with safety confirmations and detailed feedback.

Instructions

Deletes a WordPress post with options for trash or permanent deletion. Includes safety confirmations and detailed feedback on the deletion action.

Usage Examples: • Trash a post: wp_delete_post --id=123 (moves to trash) • Permanent deletion: wp_delete_post --id=123 --force=true • Bulk operations: Use multiple calls with different IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the post to delete.
siteNoThe ID of the WordPress site to target (from mcp-wordpress.config.json). Required if multiple sites are configured.
forceNoWhether to bypass trash and force deletion (default: false, moves to trash).
Behavior3/5

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

No annotations provided. Description mentions safety confirmations and detailed feedback but does not specify what they entail. Lacks disclosure of authorization needs, rate limits, or side effects beyond deletion.

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?

Description is concise with front-loaded main action. Usage examples are helpful but could be integrated more succinctly. No unnecessary repetition.

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

Completeness3/5

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

With 3 parameters and no output schema, description covers core functionality but lacks details on return values, error handling, or post-deletion state. Some gaps remain.

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 100%. Description explains the `--force` parameter and default behavior, adding meaning through examples (e.g., 'moves to trash').

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?

The description clearly states it deletes a WordPress post with options for trash or permanent deletion. It distinguishes from sibling tools like wp_delete_comment and wp_spam_comment.

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?

Usage examples show when to use trash vs permanent deletion and mention bulk operations. However, it does not explicitly state when not to use this tool or suggest alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/docdyhr/mcp-wordpress'

If you have feedback or need assistance with the MCP directory API, please join our Discord server