Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by iamsamuelfraga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_cpt_delete

Delete custom post type items by ID. Moves to trash by default; use force flag and confirmation for permanent deletion.

Instructions

Delete an item of any CPT. Default to trash. force=true with confirm="DELETE_PERMANENTLY_" for hard delete (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": {
      "post_type": "<post_type>",
      "id": "<id>"
    },
    "name": "wp_cpt_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
forceNo
confirmNo
post_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behaviors: default soft delete, the hard delete confirmation format, and the MODE=full requirement. It does not mention return values or error handling, but the disclosed behaviors are well covered.

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 a single, information-dense sentence with no fluff. It efficiently covers the action, default behavior, and hard-delete prerequisite in a compact structure.

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?

Despite four parameters, no annotations, and no output schema, the description provides essential operational details: soft delete default, hard delete confirmation format, and MODE requirement. It omits return value details and permissions, but these are less critical for a delete operation.

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

Parameters4/5

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

The schema has no descriptions, but the description explains the force and confirm interaction, and implicitly defines post_type and id through context. It adds significant meaning beyond the schema, though it could explicitly state that post_type is the CPT slug and id is the item ID.

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 an item') and specifies the resource ('any CPT'), effectively distinguishing it from sibling tools that target posts, pages, or media. The mention of default trash behavior further clarifies its function.

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?

It provides explicit guidance on default behavior (trash) and how to perform a hard delete (force=true with confirm string), including the MODE=full requirement. While it does not name alternative tools or state when not to use it, the context and name imply its scope.

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