wordpress_delete_comment
wordpress_delete_commentRemove a WordPress comment using its ID, with an option to force deletion even if it has replies.
Instructions
Delete a comment
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| commentId | Yes | ||
| force | Yes |
wordpress_delete_commentRemove a WordPress comment using its ID, with an option to force deletion even if it has replies.
Delete a comment
| Name | Required | Description | Default |
|---|---|---|---|
| commentId | Yes | ||
| force | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist; description only says 'Delete a comment'. Fails to disclose behavioral traits such as whether comments are trashed or permanently deleted, or if permission checks are involved.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely short (three words), but lacks necessary detail. Front-loaded but not sufficiently informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given two required parameters and no output schema, the description is incomplete. It omits return values, side effects, and error handling, making it insufficient for reliable tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and description adds no meaning. The 'force' parameter is not explained, leaving ambiguity about its effect. No value added beyond names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Delete a comment' with verb and resource. It distinguishes from siblings like create or update, but doesn't clarify whether deletion is permanent or moves to trash.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like bulk deletion or trashing. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RaheesAhmed/wordpress-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server