Skip to main content
Glama

Search Aukro.cz Offers (Active & Archived)

aukro_search_offers
Read-onlyIdempotent

Search active or archived Aukro.cz marketplace offers by keyword, category, price, condition, seller, location, and curated feeds; use filters to find specific listings or check sold prices.

Instructions

Search active or completed/archived (finished: true) marketplace offers on Aukro.cz. Supports keyword search, category ID/SEO URL, price bounds, offer format (auction vs buy-now vs hot auction), item condition (NEW, USED, etc.), seller username/ID, shipping/payment filters, geolocation (postCode + distanceKm), dynamic category attribute filters, and curated feeds (ENDING_SOON, FROM_1_CZK, UP_TO_300_CZK, NEW_OFFERS, POPULAR, PRICE_HITS, CHARITY, OUTLET). Works anonymously without login.

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

Input Schema

NameRequiredDescriptionDefault
pageNo0-indexed page number (0 = first page)
sortNoSorting field and directionrelevance:DESC
queryNoSearch keyword or phrase (or numeric offer ID)
queriesNoMultiple keyword query variants to execute in parallel and deduplicate by `itemId` (e.g. ['8GB', '8/128', '8/256', '12GB'])
currencyNoOverride response currency (defaults to CZK)
finishedNoWhen true, searches completed/ended/archived listings (useful for checking historical sold prices)
pageSizeNoNumber of offers per page (1..180, default 20)
postCodeNoCzech postal code (PSČ, e.g. '110 00') for radius distance filtering
priceMaxNoMaximum price in selected currency
priceMinNoMinimum price in selected currency
sellerIdNoFilter by numeric seller userId
aukroPlusNoOnly Aukro+ offers
offerTypeNoFilter by listing type: ALL, AUCTION, BUY_NOW (Kup teď), or HOT_AUCTION (Žhavé aukce)ALL
categoryIdNoNumeric category ID to filter by (from `aukro_get_categories`)
conditionsNoFilter by item condition (Stav zboží)
distanceKmNoMaximum distance in kilometers from `postCode`
sellerNamesNoFilter by one or more seller usernames (e.g. ['Alza_prodej'])
specialFeedNoFilter by curated Aukro special marketplace feed
endingWithinNoRelative time window before offer ends (e.g. '1h', '3h', '6h', '12h', '24h', '3d', '7d')
excludeWordsNoCase-insensitive words/substrings to exclude from returned offer titles (e.g. ['iphone', 'lumia', 'kryt'])
freeShippingNoOnly items with free shipping
withShippingNoWhen true, only returns offers that can be shipped (excludes personal-pickup-only listings)
cashOnDeliveryNoOnly items supporting cash on delivery (Dobírka)
categorySeoUrlNoCategory SEO slug (e.g. 'mobilni-telefony-apple')
personalPickupNoOnly items allowing personal pickup (Osobní převzetí)
paymentViaAukroNoOnly items supporting secure Payment via Aukro (Platba přes Aukro / Buyer Protection)
attributeFiltersNoDynamic category parameter/attribute filters
excludeCategoryIdsNoLeaf category IDs to exclude from results (e.g. [107152] to exclude iPhones)
includeAggregationsNoWhen true, includes category and attribute facet aggregations in the response
searchInDescriptionNoWhen true, searches inside offer descriptions as well as titles
destinationCountriesNoShipping destination country codes (e.g. ['cz', 'sk'])
priceDeliveryIncludedNoWhen true, `priceMin` and `priceMax` are evaluated against the total price including shipping (`priceWithShipping`)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent, open-world behavior, and the description adds the important operational detail that no login is required. It also explains that archived search is useful for historical sold prices, but it does not disclose result format, pagination behavior, or any rate/result limits.

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 front-loaded with the core search purpose and then packs the supported filter areas into a dense but information-rich list. It avoids fluff, though the long comma-separated feature enumeration is less structured than it could be for a 32-parameter tool.

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 complex search tool, the definition covers the major modes and filter families well, and annotations plus the rich input schema carry safety and parameter details. However, since there is no output schema, the description could do more to explain return values, pagination, or how facets are returned.

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 itself documents all 32 parameters in detail. The description groups and names major filter categories, but mostly restates capabilities already present in the schema rather than adding syntax, constraints, or combination rules beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: searching active or completed/archived marketplace offers on Aukro.cz. It clearly frames the tool as a search endpoint with broad filtering scope, making it distinguishable from detail, autocomplete, and category lookup siblings.

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

Usage Guidelines4/5

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

It gives clear usage context for active versus archived search (`finished: true`) and notes that the tool works anonymously without login. It does not explicitly route the agent to alternatives such as `aukro_get_offer_detail` or state when not to use search, so it misses full when/when-not guidance.

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