Skip to main content
Glama

wordpress_bulk_delete_posts

wordpress_bulk_delete_posts

Delete multiple WordPress posts at once by providing post IDs and force delete option. Clean up your site efficiently.

Instructions

Delete multiple posts in one operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postIdsYes
forceYes
Behavior1/5

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

No annotations exist, so the description carries full burden. It only states 'delete' without disclosing whether the operation is permanent, what the 'force' parameter does (e.g., bypass trash), or any side effects. This is critically insufficient for a data-mutating tool.

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

Conciseness2/5

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

The description is a single short sentence, which is concise but under-specified. It lacks structure for an operation with required parameters and behavioral implications, resulting in unhelpful brevity.

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

Completeness1/5

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

Given no annotations, no output schema, and two parameters with zero coverage, the description is highly incomplete. It fails to convey critical aspects like the effect of 'force', whether posts go to trash or are permanently deleted, or any confirmation requirements.

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

Parameters1/5

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

The input schema has 0% description coverage for parameters, and the tool description adds nothing about 'postIds' or 'force'. The agent receives no guidance on the meaning or expected values of these parameters beyond the schema types.

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?

The description clearly states the action ('Delete multiple posts') and resource ('posts'), with 'one operation' indicating batch processing. It distinguishes from single-deletion siblings (wordpress_delete_post) and bulk media deletion (wordpress_bulk_delete_media). However, it adds little beyond the tool name, which already conveys 'bulk delete posts'.

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 implies use for batch deletion of posts but provides no explicit guidance on when to choose this over single deletion or media deletion. No alternatives or when-not conditions are mentioned, relying on the agent to infer from the name and siblings.

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/RaheesAhmed/wordpress-mcp-server'

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