Skip to main content
Glama

delete_tag

DestructiveIdempotent

Deletes a WordPress tag by ID and optionally forces permanent removal by bypassing the trash.

Instructions

Delete a WordPress tag

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": {
      "tag_id": "<tag_id>"
    },
    "name": "delete_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce delete (bypass trash)
tag_idYesTag ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not disclose that deletion may be soft (moved to trash) unless force is set, nor what happens to posts still carrying the tag, which is exactly the extra context the annotations cannot convey.

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?

A single five-word sentence with the verb and resource front-loaded and zero filler. It is efficient rather than padded, though the brevity comes at the cost of the behavioral detail noted elsewhere.

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

Completeness3/5

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

For a two-parameter destructive tool whose annotations and schema are fully populated, minimal prose is defensible and no output schema needs explaining. Still, the reversible-vs-permanent deletion distinction and any permission requirements are absent, leaving a gap an agent could act on incorrectly.

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?

Schema description coverage is 100% — both 'tag_id' and 'force' are documented inline, with 'force' explained as bypassing trash. The description itself contributes no parameter meaning, so the baseline 3 applies; the trash-vs-permanent distinction lives only in the 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?

The description states a specific verb ('Delete') and resource ('a WordPress tag'), which is enough to tell it apart from create_tag/update_tag and, via the resource noun, from delete_category/delete_post. It stops short of any explicit sibling differentiation, so it is clear but not maximally distinctive.

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 or when-not-to-use guidance, no mention of prerequisites (e.g. needing the tag_id from get_tags), and no hint about when to prefer force deletion over the default trash behavior. An agent must infer all of this from the schema alone.

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