Skip to main content
Glama

dipscout

by com.dipscout
OverviewDiscussionsAdmin

Search AliExpress deals

buscar_promocoes
Read-onlyIdempotent

Lists AliExpress products with a real price drop, detected by our price history in the last 7 days (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.

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" or "pl". 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\" 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"
+]
  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\" 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"
+]
  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\" 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"
+]
  4. 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"
+}
  5. 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"
+}
  6. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safe read-only, idempotent profile, and the description adds real substance beyond them: the 7-day detection window, that the seller's 'was' price is explicitly excluded, and the semantics of discount.certainty ('verified' vs 'none') including the warning that a percentage without certainty misinforms. Missing only richer detail such as ordering or pagination of the returned list.

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-loaded with the core definition, then the certainty contract, which is efficient ordering. It loses a point for restating the 'seller's was price does not count' point twice in four sentences.

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 burden of explaining the returned discount.certainty field, and it does so clearly enough for an agent to use the results correctly. An agent can call the tool with zero required parameters and understand the contract; only return ordering and list size behavior remain unstated.

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 88%, so parameters are already well documented; the description adds context only for the discount semantics behind desconto_minimo and the scoping of busca. It says nothing extra about categoria, idioma, limite, or the legacy apenas_verificados flag beyond what the schema states.

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 plus the defining criterion: products whose price drop is proven by the tool's own 7-day price history. It clearly rules out seller-claimed discounts, which is the key differentiator. It does not, however, distinguish itself from the sibling tools quedas_de_preco or alternativas_mais_baratas, whose names suggest overlapping territory.

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 description implies when the tool is appropriate (you want drops that can honestly be presented as savings) and warns against quoting a percentage without certainty. But it never names an alternative or states when to pick a sibling such as historico_de_preco or avaliar_preco instead, so tool selection still requires inference.

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

All dipscout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources