mcp-wordpress

wp_comments_delete

Delete a WordPress comment by sending it to trash (recoverable) or permanently removing it with a forced confirmation.

Instructions

Delete a comment. Default to trash (recoverable). force=true with confirm="DELETE_PERMANENTLY_" permanently deletes (requires MODE=full).

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": "wp_comments_delete"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`force`	No
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses that the default action is a recoverable trash, that permanent deletion requires force=true plus a specific confirmation string, and that MODE=full is required. This gives the agent important safety-relevant behavior beyond the schema.

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

Conciseness5/5

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

The description is two sentences: the first states the core action, the second packs the behavioral details. It is front-loaded and every clause earns its place without redundancy.

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 delete tool with no annotations and no output schema, the description covers the essential decision points: default trash, permanent deletion path, and the MODE=full requirement. It does not mention return values or error handling, but for a simple comment delete operation the provided information is largely sufficient.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It explains the semantic meaning of force and confirm, including the exact confirmation format 'DELETE_PERMANENTLY_<id>', and clarifies the default of force=false. The id parameter is self-evident from the purpose, so the description adds meaningful value for all parameters.

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 opens with a specific verb and resource: 'Delete a comment.' It clearly distinguishes this from sibling tools like wp_comments_get, wp_comments_update, and wp_comments_create by stating the deletion action. The additional details about trashing and permanent deletion reinforce the tool's purpose.

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?

The description clearly explains the default behavior (trash, recoverable) and when to use force=true with the required confirmation string for permanent deletion. It does not explicitly mention alternatives or when-not-to-use, but the context is sufficient for an agent to decide when deletion is appropriate.

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

Deploy Server