Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Set term language

wordpress_set_term_language
Destructive

Assigns a language or translation link to an existing WordPress taxonomy term through the active multilingual provider, keeping term localization and translations consistent.

Instructions

[UNIFIED] Apply generic language and/or translation linking to an existing taxonomy term through the active multilingual provider adapter.

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": {
      "site": "<site>",
      "taxonomy": "<taxonomy>",
      "term_id": "<term_id>"
    },
    "name": "wordpress_set_term_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
term_idYes
languageNo
taxonomyYes
translation_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the description's job is to explain that destructiveness — it does not. It never says what gets overwritten or removed, whether clearing a language is possible, or what error occurs when no multilingual adapter is active. The single sentence adds almost no behavior beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no padding, which is structurally fine, but the leading "[UNIFIED]" tag consumes attention without conveying meaning and the sentence is too terse for the complexity involved.

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?

This is a destructive mutation with 5 undocumented parameters, no output schema, and an undisclosed dependency on an active multilingual provider. An agent cannot call it correctly from this definition alone — required identifier formats and the destructive consequences are missing.

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% across all five parameters, so the description must compensate and instead gives essentially nothing: only the vague phrase "language and/or translation linking" loosely gestures at 'language' and 'translation_of'. The required 'site', 'taxonomy', and 'term_id' parameters, and the format/semantics of 'translation_of' (a term identifier? a string?), are entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb-plus-resource ("apply language and/or translation linking to an existing taxonomy term") is present, so the agent knows this modifies an existing term rather than creating one. However, the qualifiers "[UNIFIED]" and "generic language" are jargon that do not pin down what is actually written, and the description never states which sibling (e.g. wordpress_create_taxonomy_term) is the alternative.

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?

There is no when-to-use guidance, no prerequisites (a multilingual provider plugin must presumably be active), and no statement of what happens when 'language' is null versus supplied. Nothing routes the agent between this tool and term-creation or bulk-update siblings.

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