Skip to main content
Glama

Mejorador de publicaciones (aplicar)

ml_aplicar_mejora

Rewrites a MercadoLibre listing description into a conversion-focused structure with summary, specs, box contents, and real buyer FAQs, previewing changes before saving.

Instructions

MODIFICA la descripción real de una publicación (de cualquiera de tus tiendas: encuentra sola de cuál es) con la estructura que convierte: el RESUMEN en los 5 primeros renglones (3 a 5 renglones), después MEDIDAS, CARACTERÍSTICAS PRINCIPALES, QUÉ VIENE EN LA CAJA, lo extra que haya que conservar, y al final las PREGUNTAS FRECUENTES: las 20 de los últimos 90 días con las respuestas reales del vendedor (se calculan solas). Con mismo_sku=true la aplica también a TODAS las publicaciones con el mismo SKU en todas tus tiendas conectadas, cada una con el FAQ de SUS propias preguntas. Los textos los escribe Claude con datos reales (ml_mejorar_publicacion trae el material): nunca inventar medidas ni características. Sin confirmar=true solo muestra cómo quedaría; con confirmar=true la escribe (solo con OK explícito del vendedor) y guarda antes un respaldo de cada descripción anterior. Valida: sin HTML, sin datos de contacto ni links, medidas con número y unidad.

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": {
      "item_id": "<item_id>",
      "resumen": "<resumen>",
      "medidas": "<medidas>",
      "caracteristicas": "<caracteristicas>",
      "incluye": "<incluye>"
    },
    "name": "ml_aplicar_mejora"
  }
}

Input Schema

NameRequiredDescriptionDefault
faqNofalse = no agregar las preguntas frecuentes
extraNoTexto de la descripción actual que haya que conservar (garantía, uso, cuidados)
cuentaNouser_id de la cuenta de ML si hay varias conectadas (ver ml_cuentas)
incluyeYesQué viene en la caja, un renglón por cosa
item_idYesLa publicación (MCO...)
medidasYesRenglones de medidas (ej "Alto: 27 cm")
resumenYes3 a 5 renglones: el resumen de todo el producto
confirmarNotrue = escribirla en MercadoLibre (solo con OK explícito del vendedor)
mismo_skuNotrue = aplicarla también a las publicaciones con el mismo SKU en todas tus tiendas
caracteristicasYesCaracterísticas principales, un renglón cada una

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0-tyl.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the burden and does: it discloses dry-run preview, the backup taken before each overwrite, multi-store propagation with mismo_sku, and the validation rules (no HTML, no contact info/links, measurements with number and unit). This is exactly the mutation context an agent needs.

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?

One dense paragraph, but front-loaded with the action and every sentence carries new information (structure, scope, sourcing, dry-run/confirm, backup, validation). Slightly overlong and would scan better as a few short lines, but there is no filler.

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?

With 10 parameters, no output schema, and a destructive write, the description still covers everything an agent needs: input provenance, preview vs. commit, backup, replication scope, and validation constraints. Nothing essential for a correct call 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 100%, so baseline is 3; the description still adds meaning by linking confirmar to the explicit seller OK, explaining that mismo_sku applies per-listing FAQs from each listing's own questions, and noting faq is auto-computed from the last 90 days. It does not cover cuenta or extra in detail, keeping it just below top marks.

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?

Starts with a specific verb+resource ('MODIFICA la descripción real de una publicación') and then spells out the exact target structure (resumen, medidas, características, incluye, FAQ). It clearly separates itself from ml_mejorar_publicacion by naming it as the material source and from ml_actualizar_publicacion by describing the structured rewrite.

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

Usage Guidelines5/5

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

Explicitly states the two modes: 'Sin confirmar=true solo muestra cómo quedaría; con confirmar=true la escribe (solo con OK explícito del vendedor)'. It also points to the companion tool ml_mejorar_publicacion for source data, so the agent knows the workflow order.

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