Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_taxonomy_terms

List terms for any WordPress taxonomy to organize and manage categories, tags, or custom taxonomies. Filter results by search and paginate with per_page for targeted retrieval.

Instructions

List terms for a taxonomy

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": {
      "taxonomy": "<taxonomy>"
    },
    "name": "wp_list_taxonomy_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNo
per_pageNo
taxonomyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations present, the description carries the full burden of behavioral disclosure. It reveals only that this is a listing operation, and omits behavior such as pagination via per_page, search behavior, what happens when the taxonomy does not exist, or the shape of the returned term list.

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?

The description is a single, front-loaded sentence with no redundant words. It is appropriately compact, though it could include additional parameter context without becoming bloated.

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?

For a tool with three parameters, no output schema, and no annotations, the description is too thin. It does not clarify how search works, how pagination is handled, which taxonomy identifies the source, or how the response is structured, leaving meaningful gaps for an agent deciding how to invoke it.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate by explaining the required taxonomy parameter or the optional search and per_page parameters. An agent must infer the meaning of all three parameters from their names alone.

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 uses a specific verb ('List') and a clear resource ('terms for a taxonomy'), which conveys the core operation. It is distinguishable from siblings like wp_list_taxonomies and wp_create_taxonomy_term, though it does not spell out what kinds of terms or which taxonomies are covered.

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?

No guidance is provided about when to use this tool instead of related tools such as wp_list_taxonomies, wp_list_categories, or wp_list_tags. The description states only the action and gives no context or exclusions.

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