Skip to main content
Glama

price_history

Fetches paginated price-change history for a Mercado Libre item over a selected day window, enabling review of past price movements.

Instructions

Historial de cambios de precio de una publicación de Mercado Libre (solo lectura). Devuelve los eventos de cambio de precio del item en una ventana de días, paginados. Requiere item_id; days/page/size son opcionales.

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": "price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoVentana del histórico en días (1-180, default 30)
pageNoPágina (0-based) del paginado del endpoint
sizeNoTamaño de página (1-200, default 50)
item_idYesID de la publicación en ML (ej: MLA123456789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0-alpha.3

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the safety profile and does so adequately by declaring read-only behavior and describing a paginated response of price-change events over a day window. It omits anything about permissions, rate limits, or what happens when an item has no history, which leaves real gaps for a zero-annotation tool.

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?

Two sentences, front-loaded with the resource and read-only status, then the return shape, then parameter constraint. Every clause carries information; nothing is padded.

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?

A simple read-only query with fully documented parameters and no output schema. The description covers what the tool returns (price-change events in a paginated day window) and what is required, so an agent has everything needed to call it correctly.

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 100%, so the schema already documents every parameter including defaults and ranges. The description only restates that item_id is required and days/page/size are optional, adding no format, semantics, or interaction detail beyond the schema.

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: retrieving price-change history for a Mercado Libre listing, explicitly marked as read-only. This is enough to separate it from mutating siblings like update_price, though it never names an alternative tool.

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 '(solo lectura)' tag and 'historial' framing imply it should be chosen for inspection rather than modification, and the days window implies recency scoping. There is no explicit statement of when to prefer it over price_to_win or get_item_metrics, so the agent must infer the boundary.

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