Skip to main content
Glama

create_tag

Creates a new WordPress tag with a required name and optional slug or description, helping organize content by topic.

Instructions

Create a new 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": {
      "name": "<name>"
    },
    "name": "create_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTag name
slugNoCustom slug (optional, e.g. an ASCII slug for non-ASCII names)
descriptionNoTag description (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write with no open-world access, so the safety profile is covered. The description adds nothing beyond them — notably it does not say what happens if a tag with the same name or slug already exists, which matters given idempotentHint=false.

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 action front-loaded and zero filler. It is efficient, though so terse that brevity shades into under-specification rather than crispness.

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 simple three-parameter create tool with full schema coverage and annotations, this is adequate. It is still silent on duplicate handling and on what creation returns, both of which an agent would want before calling a non-idempotent write.

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% and all three parameters carry their own descriptions, including the useful note that slug can supply an ASCII slug for non-ASCII names. The description itself adds no parameter meaning, so the baseline of 3 applies.

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 ("Create") and resource ("a new WordPress tag"), which is enough to distinguish it from siblings like create_post or create_category. It stops short of naming any sibling explicitly, but the resource noun does the differentiating work.

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 versus update_tag (for existing tags) or create_category (for a different taxonomy). The word "new" weakly implies it is not for modifying existing tags, but the agent must infer that from the sibling list rather than from the description.

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