Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

vincular_traducciones_polylang

Links two existing WordPress posts so Polylang recognizes them as the Spanish and English versions of the same article, establishing their translation relationship by post ID.

Instructions

Vincula dos artículos existentes en WordPress para que Polylang los reconozca como la versión en Español y la versión en Inglés del mismo artículo.

Args: post_id_es: ID del artículo en español. post_id_en: ID del artículo en inglés.

Returns: Confirmación del enlace entre ambas traducciones.

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": {
      "post_id_es": "<post_id_es>",
      "post_id_en": "<post_id_en>"
    },
    "name": "vincular_traducciones_polylang"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_id_enYes
post_id_esYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden. It discloses only that a confirmation is returned; it says nothing about required Polylang configuration, whether an existing link is overwritten, reversibility, or failure modes such as mismatched or missing post IDs — all critical for a mutation that changes translation relationships.

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 operative sentence is front-loaded and the Args/Returns scaffolding is easy to scan. The Args block largely duplicates the first sentence's meaning and the schema's field names, so it is slightly padded but not wasteful.

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?

The tool is simple (2 required integer params) and an output schema exists, so the description needn't explain return values. Still, for an unannotated mutation tool it omits the prerequisites (Polylang active, posts already published/existing) and the overwrite/error behavior an agent needs to invoke it safely.

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 0%, so the description must compensate, and it does list both parameters with their language roles (Spanish post ID, English post ID). That is essentially a restatement of the schema field titles, adding no format, validity, or cross-constraint detail (e.g. that the IDs must belong to different languages).

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 (vincula) and resource (dos artículos en WordPress) plus the exact effect: Polylang will treat them as the Spanish and English versions of one article. It implicitly separates itself from vincular_terminos_polylang by operating on articles rather than terms, but never names that distinction explicitly.

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?

The phrase 'dos artículos existentes' implies both posts must already exist before linking, which is useful precondition context. However there is no explicit when-to-use vs. when-not guidance, no mention of alternatives among the siblings, and no statement of what to do if the pairing is wrong.

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