Skip to main content
Glama
Sign In
MCP WordPress Server

MCP WordPress Server

by docdyhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_get_category

Retrieve a single WordPress category by its unique ID to access details and manage site taxonomy.

Instructions

Retrieves a single category by its ID.

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": {
      "id": "<id>"
    },
    "name": "wp_get_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe unique identifier for the category.
siteNoThe ID of the WordPress site to target (from mcp-wordpress.config.json). Required if multiple sites are configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.23
  2. Removedv3.3.22
  3. Addedv3.3.8
  4. Removedv3.3.7
  5. Changed1 schema field changedv3.3.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  6. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose side effects or permissions, but it only states the basic operation. It does not mention if there are any restrictions or returns.

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?

Single sentence, no wasted words. Front-loaded with key action.

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?

Without an output schema, the description should hint at the return structure (e.g., WP_Term). It is adequate for a simple retrieval but lacks completeness.

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 coverage is 100%, so the description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool retrieves a single category by its ID. It uses a specific verb and resource, though it doesn't distinguish from the few related siblings like wp_update_category.

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 on when to use this tool versus alternatives, nor any context about prerequisites 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