Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a term

delete_term
Destructive

Permanently delete a taxonomy term after confirmation. Assigned content loses the term but is not deleted.

Instructions

Delete a term from any taxonomy. Terms have no trash — deletion is immediate and permanent, so this reports what will be affected and requires confirm: true. Content assigned to the term is not deleted; it simply loses the assignment (posts losing their only category fall back to the default category).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe term ID to delete.
confirmNoRequired — term deletion cannot be undone.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
taxonomyNoTaxonomy slug or REST base (category, post_tag/tags, or a custom one).category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond destructiveHint=true by disclosing that terms have no trash, deletion is immediate and permanent, the tool reports what will be affected and requires confirm:true, and that content assignments are orphaned rather than deleted, with fallback to the default category. No contradiction with annotations.

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?

Three sentences, starting with purpose, then the critical safety warning about permanent deletion, and finally the content side-effect. Every sentence adds meaningful information with no redundancy.

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?

Covers purpose, side-effects on content, and the confirmation requirement—sufficient for safe invocation. Does not describe the response shape beyond 'reports what will be affected,' but with no output schema that is a minor gap.

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

Parameters3/5

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

The input schema already covers all four parameters with descriptions, so the description adds little parameter-level detail. It reinforces that confirm:true is required and explains the reason, which provides some context beyond the schema's 'required' label, but no additional format or valid-value guidance is given.

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?

States a concrete action, object, and scope: 'Delete a term from any taxonomy.' Differentiates from sibling delete_* tools (delete_content, delete_media) by specifying the resource type, and from update_term by stating deletion rather than modification.

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?

Describes the finality of the operation and that confirm is required, but does not explicitly identify alternatives or conditions for choosing this tool over siblings. The context makes the use case clear, yet no when-not guidance or alternative routing is provided.

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