Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

vincular_terminos_polylang

Links Spanish and English category or tag terms in Polylang Free so WordPress recognizes them as translations and displays the correct taxonomy per language.

Instructions

Vincula dos términos taxonómicos (categorías o etiquetas) en Polylang Free para que se reconozcan como versiones traducidas en Español e Inglés.

Args: termino_id_es: ID del término en español. termino_id_en: ID del término en inglés. taxonomia: 'category' para categorías o 'post_tag' para etiquetas.

Returns: Confirmación del enlace en Polylang.

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": {
      "termino_id_es": "<termino_id_es>",
      "termino_id_en": "<termino_id_en>"
    },
    "name": "vincular_terminos_polylang"
  }
}

Input Schema

NameRequiredDescriptionDefault
taxonomiaNocategory
termino_id_enYes
termino_id_esYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the effect (an EN/ES term link is registered in Polylang) and that a confirmation is returned, but says nothing about whether an existing link is overwritten, whether the operation is idempotent, what permissions are needed, or what happens on failure — all material for a mutation tool.

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 purpose sentence is front-loaded and precise, followed by a compact Args list that earns its place by adding the enum values the schema lacks. The 'Returns' line is largely redundant given an output schema exists, but the overall definition is short and free of padding.

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?

For a three-parameter mutation with no annotations but an output schema, the description covers purpose and all parameters adequately. It is still thin on preconditions (terms existing, plugin state) and side effects (relinking/overwriting existing translations), which an agent would need before calling it confidently.

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?

With 0% schema description coverage, the description compensates well: it explains that termino_id_es and termino_id_en are the term IDs in each language, and crucially documents that taxonomia accepts 'category' or 'post_tag'. That accepted-values guidance is absent from the schema (which only shows a string with default 'category'), so real meaning is added.

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?

States a specific verb+resource: linking two taxonomy terms (categories or tags) so Polylang recognizes them as Spanish/English translations. That resource specificity distinguishes it in principle from vincular_traducciones_polylang, but the description never names that sibling explicitly, leaving the agent to infer the split.

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 implied by the purpose statement (use it when taxonomy terms need to be paired as translations) and the mention of 'Polylang Free' hints at a plugin-availability context. However, no explicit when-to-use/when-not guidance, prerequisites (both terms must already exist, Polylang must be active), or alternative sibling is offered.

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