Skip to main content
Glama

update_tag

DestructiveIdempotent

Modify an existing WordPress tag by ID, including its name, slug, or description. Use it to correct or refresh tag details without creating a new tag.

Instructions

Update an existing 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": "update_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew tag name (optional)
slugNoNew slug (optional; WordPress does not auto-update the slug when the name changes)
tag_idYesTag ID to update
descriptionNoNew tag description (optional)

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, but the description adds nothing beyond them. It never explains what is destructive about an update, whether unspecified fields (name, slug, description) are left intact or cleared, or what happens when tag_id does not exist.

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 front-loaded sentence with zero filler or repetition of schema content. It is compact and unambiguous as far as it goes.

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?

This is a destructive mutation over four parameters with no output schema, yet the description is one sentence with no mention of overwrite semantics, partial-update behavior, or failure modes. It leaves the agent without the behavioral context that the annotations alone cannot supply.

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%, so every parameter including the slug/name non-propagation caveat is already documented in the schema. The description contributes no additional parameter meaning, which is the baseline expectation when the schema does the work.

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 (Update) and resource (an existing WordPress tag), which is enough to separate it from create_tag and delete_tag. It stops short of naming any sibling or scoping what parts of the tag can be updated, so it is clear rather than differentiating.

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 instead of create_tag, update_category, or delete_tag, and no stated prerequisites such as the tag needing to exist or permissions required. The only implied context comes from the word 'existing'.

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