Skip to main content
Glama
RaheesAhmed

WordPress MCP Server

by RaheesAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it fails to mention whether posts are permanently deleted or moved to trash, the role of the 'force' parameter, or any side effects. This is a destructive operation without safety context.

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?

The description is a single, concise sentence that is easy to parse and front-loaded. However, it omits critical details, so it is concise but under-specified.

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?

The tool has no annotations and no output schema, so the description must compensate. It does not cover permanence, return values, or parameter semantics, making it inadequate for a destructive bulk operation.

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 schema defines postIds and force with no descriptions, and schema description coverage is 0%. The description does not explain these parameters at all, leaving the agent without necessary information about their format or meaning.

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 the action (delete), the resource (posts), and the scope (multiple, one operation). This distinguishes it from sibling wordpress_delete_post, which targets a single post.

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 guidance on when to use this tool versus alternatives like wordpress_delete_post, nor any mention of prerequisites or exclusions. The description only states the function, leaving usage context to inference.

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

Deploy Server

Other Tools