Skip to main content
Glama

wintraits_diagnosticar_producto

Why isn't my product selling? What should I change in my listing? (¿Por qué no vende mi producto? ¿Qué cambio en mi ficha?)

Match categories (disponibles). Diagnoses a product listing (Amazon, an own shop, another marketplace or a draft): Wintraits Match Index (similarity to winners, 0-100, not a sales probability; always call it by that name, indice_match.texto), the changes that raise it most and the winning combinations within reach (missing one or two elements). On the free plan you see the first changes; bloqueado says how many more the full report has and acceso which view was used.

Optional atributos: if you (the AI) read the listing yourself, call wintraits_opciones_concepto first and follow its instrucciones_extraccion: use only what the listing says (never deduce), exactly the keys of atributos and, for lista/categoria, only their valores; omit anything the listing does not say (we read it from the text). Invalid keys or values return an error with the valid options.

Args: titulo: listing title. precio_eur: selling price in euros. num_imagenes: number of images in the listing. vinetas: bullet points of the listing. descripcion: listing description. volumen_ml: volume in ml, if not in the text. atributos: optional {key: value} read from the listing (keys and values from wintraits_opciones_concepto). categoria: subcategory (see wintraits_categorias_disponibles; e.g. "serums"). pais: country code (see wintraits_categorias_disponibles; e.g. "ES"). lang: "es" (default) or "en" (attribute names in English).

Free and unlimited during the beta (until 2027-01-31). Gratis y sin límite durante la beta (hasta el 31-ene-2027).

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": {
      "titulo": "<titulo>",
      "precio_eur": "<precio_eur>"
    },
    "name": "wintraits_diagnosticar_producto"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoes
paisNoES
tituloYes
vinetasNo
atributosNo
categoriaNoserums
precio_eurYes
volumen_mlNo
descripcionNo
num_imagenesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that results are truncated on the free plan, that `bloqueado` counts withheld changes and `acceso` reports which view was used, that invalid keys/values return an error listing valid options, and that the index is not a sales probability and must be referred to by a specific name. It does not cover auth, rate limits or latency, but the behavioral surface of the response is well disclosed.

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 user question, then the diagnosis contract, then the optional-atributos workflow, then a clean Args list — a sensible order for an agent scanning top-down. It loses a little to bilingual duplication of the headline question and the beta notice, plus a parenthetical about the name requirement that could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter diagnostic with no annotations and no output schema, the description covers trigger, inputs, extraction rules, and the key response fields (`indice_match.texto`, `bloqueado`, `acceso`). It does not enumerate the remaining report structure, so an agent still learns part of the return shape only after calling, but nothing needed to invoke it correctly 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 description coverage is 0%, so the description must compensate, and it does: every one of the 10 parameters appears in the Args block with added meaning, including cross-references (categoria and pais point to wintraits_categorias_disponibles, lang switches attribute names to English) and the extraction rules for `atributos` (only what the listing says, never deduce, only listed `valores`, omit absent fields). Only `titulo` and `precio_eur` get bare restatements, which keeps it below a 5.

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?

States a specific verb and resource (diagnoses a product listing across Amazon, own shop, marketplace or draft) and names the concrete deliverable: a Wintraits Match Index 0-100 plus the changes that raise it. It also names the sibling tools it depends on (wintraits_opciones_concepto, wintraits_categorias_disponibles), so an agent can tell it apart from the chequeo/comparar/evaluar siblings without opening schemas.

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?

Gives a clear triggering question ('Why isn't my product selling?') and an explicit prerequisite workflow for the optional `atributos` path: call wintraits_opciones_concepto first and follow its `instrucciones_extraccion`. It stops short of saying when to prefer a sibling like wintraits_chequeo_rapido or wintraits_evaluar_concepto instead, so the routing is only partially specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources