Skip to main content
Glama

royal-mcp__wp_update_term_meta

Destructive

Update term meta data. Common keys for SEO plugins: Yoast uses _yoast_wpseo_title / _yoast_wpseo_metadesc; Rank Math uses rank_math_title / rank_math_description; AIOSEO uses _aioseo_title / _aioseo_description. Other protected keys (leading underscore) need an administrator to list them under Royal MCP Pro > Settings > Writable protected meta keys. String values may contain safe HTML (same allow-list as post content). Use the royal_mcp_meta_value_sanitizer filter to customize per meta key. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.

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": {
      "term_id": "<term_id>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "royal-mcp__wp_update_term_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueYes
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
term_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered; the description goes further by disclosing the human-approval gate ('nothing on the site changes until then'), the HTML allow-list on values, the sanitizer filter, and that underscore-prefixed keys require an administrator to enable. That is meaningful behavioral context beyond structured fields. It stops short of stating whether an existing value is overwritten or merged, which matters for a non-idempotent destructive write.

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 core action leads, followed by parameter-level detail, with the approval caveat saved for last. Each sentence contributes a distinct fact (key names, protected-key prerequisite, HTML policy, filter hook, approval gate) and none restates the name or annotations.

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

Completeness4/5

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

For a four-parameter destructive write with no output schema, the description covers the non-obvious risks (approval gating, protected keys, HTML sanitization) well enough to call it competently. The remaining gaps are the untyped value handling and the absence of any statement about what a successful update returns or how conflicts are resolved.

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 description coverage is only 25%, so the description must carry weight: it does add real meaning for `key` (common Yoast/Rank Math/AIOSEO key names) and for `value` (string values accept safe HTML per the post-content allow-list). However, `term_id` is never explained and there is no guidance on the accepted value types despite the schema allowing objects, arrays, and null.

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 first sentence states a specific verb+resource ('Update term meta data'), and the following sentences disambiguate the two non-obvious parameters with concrete SEO key examples. It is clear this targets metadata attached to a term, not the term itself, though it never explicitly distinguishes itself from its sibling wp_update_term or wp_update_seo_meta by name.

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 must infer that this is the tool for per-term meta key/value writes. There is no explicit 'use this instead of X' routing against neighbors like wp_update_post_meta or wp_update_seo_meta, and no statement of when a term meta write is the wrong choice. The protected-key prerequisite is a genuine context hint but is a constraint, not selection guidance.

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