Skip to main content
Glama

Price history for a product

historico_de_preco
Read-onlyIdempotent

Observed price series for an AliExpress product. Accepts the itemId or the product URL. Also returns the number of readings and days of tracking: with too little tracking there is no basis to claim a drop, and the response says so explicitly. queda is the latest drop (last 30 days) with when we detected it and the last reading that confirmed it (ISO 8601, UTC); null without a drop.

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": {
      "produto": "<produto>"
    },
    "name": "historico_de_preco"
  }
}

Input Schema

NameRequiredDescriptionDefault
idiomaNoOptional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): "en" (default), "de", "pt", "es", "fr", "ko", "it", "pl", "ja", "nl", "he" or "ar". Field names, numbers and currency (USD) are the same in every language.en
produtoYesNumeric AliExpress product_id, or the product URL (https://www.aliexpress.com/item/<product_id>.html).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\" or \"pl\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\", \"pl\", \"ja\", \"nl\", \"he\" or \"ar\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es",
      -  "fr",
      -  "ko",
      -  "it",
      -  "pl"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr",
      +  "ko",
      +  "it",
      +  "pl",
      +  "ja",
      +  "nl",
      +  "he",
      +  "ar"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\" or \"fr\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\", \"fr\", \"ko\", \"it\" or \"pl\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es",
      -  "fr"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr",
      +  "ko",
      +  "it",
      +  "pl"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\" or \"es\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\", \"es\" or \"fr\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt",
      -  "es"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es",
      +  "fr"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / idioma / description
      Previous value: -"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\" or \"pt\". Field names, numbers and currency (USD) are the same in every language."New value: +"Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\", \"pt\" or \"es\". Field names, numbers and currency (USD) are the same in every language."
    • changedInput schema / properties / idioma / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "pt"
      -]New value: +[
      +  "en",
      +  "de",
      +  "pt",
      +  "es"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / idioma
      Added value: +{
      +  "default": "en",
      +  "description": "Optional language for the human-readable text (title, discount.explanation, discount.warning, pageUrl): \"en\" (default), \"de\" or \"pt\". Field names, numbers and currency (USD) are the same in every language.",
      +  "enum": [
      +    "en",
      +    "de",
      +    "pt"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, and the description adds useful return semantics beyond that: it returns reading count and tracking days, explicitly flags insufficient tracking, and explains the `queda` field including its 30-day window, timestamps, and null state.

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?

The description is compact and front-loads the core purpose before explaining return behavior. The final sentence is dense but relevant, and there is little wasted wording.

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 read-only, two-parameter tool without an output schema, the description covers the key return semantics and the insufficient-tracking caveat. It does not describe the full price-series response shape, but it provides enough context to call and interpret the tool 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%, and both parameters are documented in the schema. The description adds little beyond the schema for `produto` and does not mention the `idioma` parameter, so it meets the baseline for fully documented parameters rather than adding substantial meaning.

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?

The description clearly states it returns an observed price series for an AliExpress product and accepts either an itemId or product URL. It is specific about the resource and scope, but does not explicitly distinguish this tool from siblings such as quedas_de_preco or menor_preco.

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

Usage Guidelines2/5

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

The description implies this is for retrieving historical price data, but gives no explicit when-to-use or when-not-to-use guidance and does not name any alternative sibling tool. The note about insufficient tracking is interpretive guidance, not selection guidance.

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