Skip to main content
Glama

Preguntas frecuentes en la descripción

ml_faq_descripcion

Creates a FAQ section from actual buyer questions and answers, groups similar queries, prioritizes frequent ones, and excludes time-sensitive data; preview or apply to a MercadoLibre listing.

Instructions

Contempla las preguntas que te hacen los compradores en una publicación y las agrega a su descripción como "PREGUNTAS FRECUENTES", con TUS respuestas reales (nunca inventa). Agrupa las parecidas, prioriza las que más se repiten, descarta lo que cambia con el tiempo (stock, precio, cuotas, envíos) y toda respuesta con datos de contacto, y no repite lo que la descripción ya cubre. El bloque queda marcado: se puede actualizar cada quincena sin duplicar. Sin aplicar=true solo MUESTRA la propuesta; con aplicar=true modifica la descripción real (pedir confirmación antes). Con todas=true toma las publicaciones que Lucía marcó en su última auditoría.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ml_faq_descripcion"
  }
}

Input Schema

NameRequiredDescriptionDefault
todasNoTodas las publicaciones que Lucía marcó con preguntas repetidas faltantes en su última auditoría
cuentaNouser_id de la cuenta de ML si hay varias conectadas (ver ml_cuentas)
maximoNoMáximo de preguntas en el bloque (default 8)
aplicarNotrue = escribir la descripción nueva en MercadoLibre (solo con confirmación explícita del vendedor)
item_idNoLa publicación (MCO...)
min_vecesNoMínimo de veces que se repitió una pregunta para entrar (default 2; 1 = todas las respondidas)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0-tyl.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=false: it discloses the mutation only happens with aplicar=true and requires explicit confirmation, that the written block is delimited so it can be refreshed biweekly without duplication, and what is deliberately excluded from the block (stock, price, installments, shipping, contact data, anything already in the description). This is exactly the kind of pre-call context a mutation tool 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?

Front-loads the core action and packs the filtering rules, idempotent block behavior and dry-run/write switch into a tight run of clauses with no filler. It is a single dense paragraph, though, so the safety-critical confirmation rule sits mid-sentence rather than being visually separated.

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?

For a 6-parameter, zero-required mutation tool with no output schema, the description covers selection scope, defaults-driven filtering intent, write safety and re-run behavior. The only residual gap, the exact shape of the proposal returned in preview mode, is minor given that no output schema exists and preview text is self-describing.

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 the baseline is 3; the description earns above that by explaining the semantic difference between the aplicar modes and by clarifying that todas targets Lucía's last-audit flagged listings rather than an arbitrary set. It leaves maximo and min_veces' effect on filtering entirely to the schema, and does not say what happens when neither item_id nor todas is supplied despite zero required parameters.

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?

Names a specific verb chain (take buyer questions, group, prioritize, filter, insert as a marked FAQ block into the listing description) plus the distinctive constraint that answers must be the seller's real ones and never invented. An agent can distinguish this from ml_preguntas (reads questions), ml_responder_pregunta (answers them) and ml_actualizar_publicacion (generic description edit) without opening any schema.

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

Usage Guidelines4/5

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

"Sin aplicar=true solo MUESTRA la propuesta; con aplicar=true modifica la descripción real (pedir confirmación antes)" gives an explicit when-to-use rule for the dry-run vs write path, and todas=true is scoped to Lucía's flagged listings. No sibling tool is named as an alternative, so an agent gets conditions but not a routing decision against ml_mejorar_publicacion or ml_actualizar_publicacion.

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