Skip to main content
Glama

Opus Growth, Ad Platforms MCP Connector

WordPress Categories & Tags

wordpress_terms
Destructive

Manage the CATEGORIES and TAGS of a connected WordPress site: list them, create one, rename it, change its slug, set its DESCRIPTION, move it under a parent, or delete it. action: 'list' (default) | 'create' | 'update' | 'delete'.

    The description is the only body text a category archive has. Without it the archive is a
    bare list of post titles, which is why category pages usually rank for nothing even when
    the posts under them do — so a new category is worth two sentences here. For the archive's
    SEO title, meta description, focus keyword or noindex use wordpress_set_seo with term_id.

On a MULTILINGUAL site every language has its OWN term — the Turkish "Apostil ve Tasdik" and its English counterpart are two different terms with two different ids — so each row carries a language field and all languages are listed together; pass lang to narrow to one. list also reports each term's post count, its live archive URL and its current SEO fields, so you can see in one call which categories are empty or unoptimised. On create and update lang does more than filter: it SETS the term's language, which is what puts an English category on the /en/ archive base instead of the site's default language. Setting the language needs Opus Growth Connector 0.7.9 on the site; on an older one the call is REFUSED before anything is written, because there lang is silently ignored and the term lands in the site's default language with the wrong archive URL. Creating a term that already exists returns the existing one instead of failing. Changing a slug CHANGES the archive URL and the reply says so explicitly, because the old address then returns 404 and needs a redirect. Deleting a term never deletes posts — it only removes the link, and the reply tells you how many posts were affected. delete needs confirm=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
nameNo
slugNo
actionNolist
parentNo
searchNo
confirmNo
term_idNo
site_urlNo
taxonomyNocategory
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. Added
  24. Removed
  25. Added
  26. Removed
  27. Added
  28. Removed
  29. Added
  30. Removed
  31. Added
  32. Removed
  33. Added
  34. Removed
  35. Added
  36. Removed
  37. Added
  38. Removed
  39. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply destructive/openWorld/idempotent flags; the description adds substantial behavior beyond them — create-on-existing returns the existing term rather than failing, slug changes break the old archive URL and regress to 404 requiring a redirect, delete unlinks but never deletes posts and reports the affected count, and the older-connector case is REFUSED before any write because lang would be silently ignored.

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?

Front-loaded with the verb/action list, then behavioral caveats, which is the right order. It is long and contains prescriptive SEO editorial ('a new category is worth two sentences here') that is tangentially motivational rather than operational, slightly diluting the density.

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

Completeness5/5

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

For a complex multi-action, 11-parameter mutation tool with an output schema, the description covers action routing, multilingual token handling, idempotency, URL/redirect side effects, delete safety, and prerequisites. An agent has everything needed to pick the right action and anticipate the reply content.

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?

With 0% schema description coverage the description must carry the load, and it does for most parameters: action values, lang (both filter and set semantics, with the version caveat), slug (URL impact), description (SEO purpose), parent, term_id (for handoff to wordpress_set_seo), and confirm. However, name, search, site_url, and the taxonomy default are never explained, leaving several of the 11 params undocumented in both schema and description.

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?

Opens with a specific verb+resource ('Manage the CATEGORIES and TAGS of a connected WordPress site') and enumerates the operations covered under a single tool (list, create, rename, slug change, description, parent move, delete) with the action enum spelled out. An agent can tell this apart from neighboring post/page/plugin tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes SEO-title/meta-description/focus-keyword/noindex work to wordpress_set_seo with term_id, and explains the two distinct uses of lang (filter on list vs. SET on create/update). It also states the precondition (Opus Growth Connector 0.7.9) and the consequence of not meeting it, plus confirm=true for delete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.