Skip to main content
Glama

mcp_delete_cpt_post

Deletes any WordPress post type by site and ID, sending it to trash by default or permanently removing it when force is enabled.

Instructions

Delete a post of any post type (moves to trash unless force is true)

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": {
      "site": "<site>",
      "type": "<type>",
      "id": "<id>"
    },
    "name": "mcp_delete_cpt_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID
siteYesSite id (see list_sites)
typeYesPost type name (e.g. post, page, product, testimonial)
forceNoSkip trash and permanently delete (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.14.0
    • removedInput schema / properties / force / default
      Removed value: -false
    • changedInput schema / properties / force / description
      Previous value: -"Skip trash and permanently delete"New value: +"Skip trash and permanently delete (default false)"
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / type / description
      Previous value: -"Post type name"New value: +"Post type name (e.g. post, page, product, testimonial)"
    • addedInput schema / properties / type / pattern
      Added value: +"^[a-zA-Z0-9_-]+$"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "type",
      -  "id"
      -]New value: +[
      +  "site",
      +  "type",
      +  "id"
      +]
  3. First observedv2.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add the important detail that the default is a soft delete to trash and that force=true is permanent, which is exactly the kind of consequence an agent needs. However, it says nothing about required permissions, what happens to attached terms/meta/comments, or whether the operation is recoverable after force.

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?

A single sentence with zero padding, and the most consequential clause (trash by default, force to purge) is placed up front in parentheses.

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 4-parameter delete tool with full schema coverage and no annotations, the definition covers purpose, scope, and the destructive default. What is missing is edge-condition context: what happens to child/related data, whether force can be undone, and error behavior when the id is invalid.

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 100% and every parameter (id, site, type, force) is documented in the schema itself, so the schema already does the heavy lifting. The description still reinforces the force semantics, which keeps it aligned with the strongest baseline for a fully documented schema.

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?

States a specific verb (delete) and resource (a post of any post type), plus a scoping note about trash vs force. It does not distinguish itself from the several delete siblings (wp_delete_post, seo_delete_post_seo), so it falls short of a 5.

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 when-to-use guidance and no mention of alternatives such as wp_delete_post, nor any stated preconditions (capabilities, whether the post must exist). The parenthetical on trash/force is behavioral context rather than routing guidance.

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