Skip to main content
Glama

Search AliExpress deals

buscar_promocoes
Read-onlyIdempotent

Lists AliExpress products with a real price drop, detected by our price history in the last 30 days and still holding (the seller's 'was' price does not count). Each product includes discount.certainty: 'verified' means the drop is proven by the time-weighted median of our readings and MAY be presented as savings; 'none' means there is no discount that can be claimed. The seller's 'was' price on the listing does not support any discount here. Quoting the percentage without the certainty next to it misinforms the reader.

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

Input Schema

NameRequiredDescriptionDefault
buscaNoText to look for in the title, only among the top drops read (up to 100); this is not a search of the whole catalog.
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
limiteNo
mercadoNo"us": only US listings, which ship within the United States only. "global": only listings that ship worldwide. Omit for both. For a shopper outside the US, use "global". Prices are always the ones read for the US.
categoriaNoCategory slug. Omit to search all categories.
preco_maximoNoMaximum price in US dollars.
desconto_minimoNoMinimum real drop, in percent, against the typical price we measured.
apenas_verificadosNoKept for compatibility: since 2026-10-14 this tool only returns products whose drop our price history proves.

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. Changed1 schema field changed
    • addedInput schema / properties / mercado
      Added value: +{
      +  "description": "\"us\": only US listings, which ship within the United States only. \"global\": only listings that ship worldwide. Omit for both. For a shopper outside the US, use \"global\". Prices are always the ones read for the US.",
      +  "enum": [
      +    "us",
      +    "global"
      +  ],
      +  "type": "string"
      +}
  7. First observed

TDQS

A3.9/5.0
Behavior5/5

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

The description adds substantial behavior beyond the read-only annotations: it explains the 30-day price-history detection method, that the drop must still be holding, and that seller 'was' prices are excluded. It also defines the discount.certainty return values and warns that percentages must be paired with certainty to avoid misleading readers.

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 purpose is front-loaded and the critical presentation warning is clear. The description is somewhat repetitive, repeating that the seller's 'was' price does not count, but the redundancy reinforces an important caveat rather than obscuring the definition.

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?

With no output schema, the description carries the important burden of explaining discount.certainty semantics and the distinction between verified and non-claimable discounts. It is complete enough for correct invocation and interpretation, though it does not describe other returned fields or ordering behavior.

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 88%, so the input schema already explains the parameters in detail. The description reinforces what a real drop means for filters like desconto_minimo and apenas_verificados, but it does not add syntax or format 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?

The description states a specific verb and resource: it lists AliExpress products with a real price drop verified by the tool's price history. It clearly distinguishes real drops from the seller's 'was' price, but it does not explicitly differentiate itself from similarly named 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 Guidelines3/5

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

Usage is implied by the description: use this tool when looking for products with verified real price drops, and do not present discounts without the certainty field. However, there is no explicit when-to-use versus alternatives guidance and no named sibling routing.

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