Royally

royal-mcp__wp_get_term

Read-onlyIdempotent

Get one term by ID and taxonomy: id, name, slug, description, count, parent and link. Term meta comes back in meta (sensitive values redacted) when you can manage categories; otherwise meta_included is false. A term that does not exist and a term in another taxonomy give the same error. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

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>",
      "taxonomy": "<taxonomy>"
    },
    "name": "royal-mcp__wp_get_term"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Term ID.
`site_id`	No	Site to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
`taxonomy`	Yes	Taxonomy slug the term belongs to (e.g. category, post_tag, product_cat).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses capability-gated behavior (meta returned only when you can manage categories, otherwise meta_included is false) and redaction of sensitive meta values. It also documents a non-obvious error semantic: a missing term and a term in the wrong taxonomy produce the same error, which prevents wasted retry loops.

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 return fields are front-loaded and the sentences are dense with distinct information. The trailing "(site: demo.royalplugins.com)" and "read-only, runs straight away" partially restate the enum and the readOnlyHint annotation, which is minor waste in an otherwise tight description.

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?

With no output schema, the description carries the burden of describing the response and does so: it lists the returned fields and explains the conditional meta/meta_included shape. Error behavior and permission gating round out what an agent needs before calling a three-parameter read tool.

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 id, taxonomy, and site_id are already documented, and the baseline is 3. The description adds a little meaning by tying taxonomy to error behavior (a term from another taxonomy fails identically to a missing one), but adds no format or syntax detail beyond the schema.

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?

"Get one term by ID and taxonomy" states a specific verb and resource and enumerates the returned fields (id, name, slug, description, count, parent, link), which implicitly separates it from list tools like wp_get_terms. It never names a sibling or an alternative, so the differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-term lookup when it already has a term ID and taxonomy slug. There is no explicit when-to-use/when-not or pointer to wp_get_terms for listing or wp_get_term_meta for raw meta.

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

All Royally tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?