Skip to main content
Glama

Detalle de una publicación

ml_publicacion
Read-only

Fetch full details of a MercadoLibre Colombia listing—price, stock, sales, type, warranty, shipping, and link—using its item ID.

Instructions

Detalle completo de una publicación: precio, stock, ventas, tipo, garantía, envío, link.

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>"
    },
    "name": "ml_publicacion"
  }
}

Input Schema

NameRequiredDescriptionDefault
cuentaNouser_id de la cuenta de ML si hay varias conectadas (ver ml_cuentas)
item_idYesID del ítem, ej: MCO123456789

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0-tyl.1

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a pure detail read, so annotations carry the safety profile. Beyond that, the description discloses the specific data payload returned (price, stock, sales, type, warranty, shipping, link), which is genuinely useful since there is no output schema. It says nothing about error behavior for invalid item IDs or cross-account access.

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?

A single front-loaded sentence whose field enumeration earns its place. The opening phrase 'Detalle completo de una publicación' partially restates the title, a minor redundancy, but nothing else is wasted.

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 simple two-parameter read tool with annotations and full schema coverage, the field list compensates reasonably for the absent output schema. It lacks guidance on multi-account disambiguation (when to pass cuenta) and on how it relates to the sibling list/update tools, which keeps it short of a 5.

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 coverage is 100% — item_id has a format example (MCO123456789) and cuenta points to ml_cuentas — so the schema does the heavy lifting. The description adds no parameter-level meaning of its own, making the baseline 3 correct.

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 and resource ('Detalle completo de una publicación') and enumerates the fields returned (precio, stock, ventas, tipo, garantía, envío, link), which lets an agent tell it apart from the plural list tool ml_publicaciones. It never names a sibling explicitly, so differentiation relies on the singular-vs-plural naming convention.

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 only implied: the required item_id plus 'detalle' suggests calling it when you already have a single item ID and need a full record. There is no explicit when-to-use, no exclusion, and no pointer to ml_publicaciones for listing or ml_actualizar_publicacion for changes.

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