Skip to main content
Glama

mcp-easy-ai__wp_get_term_meta

Read-only

Gets meta for a term. Required: term_id. Optional: key (single key — omit to return all meta), single (boolean, only with key, default true: the first value; false: every value stored under the key, as a list). When key is given, returns { term_id, taxonomy, key, value }; when key is omitted, returns { term_id, taxonomy, meta (array of key=>values), withheld_count } — withheld_count is how many protected keys (leading underscore) were left out because reading them needs manage_options (0 when nothing was left out). Read access is governed by the taxonomy's edit_terms capability. Useful for reading per-tag/per-category SEO meta from Yoast (yoast_wpseo), Rank Math (rank_math_), AIOSEO (aioseo*), or WooCommerce category images / brand logos. Through Royally: its server marks it read-only, so it runs straight away.

Input Schema

NameRequiredDescriptionDefault
keyNoOptional single meta key to retrieve. Omit to return all meta.
singleNoOnly together with `key`. true (the default when omitted): `value` is the first value stored under the key ("" when there is none). false: `value` is the list of every value stored under the key ([] when there is none). Without `key` every value of every key is returned, so sending `single` without `key` is refused.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
term_idYesThe ID of the term to retrieve meta for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint, it discloses that protected underscore keys are counted in withheld_count and require manage_options, and that read access is governed by the taxonomy's edit_terms capability — auth and filtering semantics an agent cannot get from annotations.

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?

The required parameter is stated first, then optional parameters, then return shapes, then permissions, then use cases. Dense but every clause carries load-bearing information.

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?

There is no output schema, yet the description fully specifies both response shapes including withheld_count, and covers auth and side-effect-free execution — nothing an agent needs to call it correctly is missing.

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?

Schema coverage is already 100%, but the description still adds value by explaining the interaction between key and single, the default true behavior, and the exact response shape each combination produces.

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?

States a specific verb and resource ('Gets meta for a term') and immediately scopes it with the exact return shapes for both the keyed and unkeyed cases, making it clearly distinguishable from post/user-meta siblings in the fleet.

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

Usage Guidelines4/5

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

Gives concrete applicability examples (Yoast _yoast_wpseo_*, Rank Math, AIOSEO, WooCommerce category images/brand logos) and explains the key-vs-no-key decision. It does not explicitly name sibling alternatives to avoid, so it stops short of a 5.

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.

Resources