Skip to main content
Glama

Get Full Aukro Offer Detail (Single or Batch)

aukro_get_offer_detail
Read-onlyIdempotent

Fetch complete Aukro.cz offer details for one or multiple IDs, including active or archived listings, prices, shipping, description, images, and seller summary.

Instructions

Fetch complete details for one (offerId) or multiple (offerIds, up to 20 fetched concurrently) Aukro.cz offers (works for both active and ended/archived offers). Returns unified price, next minimum bid, Buy Now price, shippingSummary (canShipToCz, cheapestShipping, totalPriceWithCheapestShipping, personalPickupAvailable), plain-text description, attributes, image URLs, shipping options, payment methods, buyer protection fees, and seller profile summary.

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_get_offer_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
offerIdNoNumeric offer / item ID (e.g. 7140475083)
currencyNoOverride response currency (defaults to CZK)
offerIdsNoBatch of up to 20 numeric offer IDs to fetch in parallel
maxDescriptionLengthNoMaximum character length of plain-text description (defaults to 2500 for single offer, 1200 for batch)
includeHtmlDescriptionNoWhen true, also includes the raw `descriptionInHtml` field
includeInternationalShippingNoWhen true, includes shipping options for all foreign destination countries (by default only domestic CZ options are listed in `shippingOptions`, while foreign country codes are listed in `shippingSummary.internationalCountriesAvailable`)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine context beyond that: it works on ended/archived offers, batches fetch up to 20 concurrently, defaults to CZK, and enumerates the returned data (shipping summary, buyer protection fees, seller profile) so the agent knows the payload's shape without an output schema.

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?

It is a single dense sentence, but the mode selection and the return inventory are front-loaded and every clause carries information. The long enumeration of returned fields is justified by the absence of an output schema, though it could be broken into two sentences for readability.

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 six-parameter read tool with no output schema, the description does the heavy lifting by listing return contents and noting active/archived coverage. Minor gaps remain: it doesn't say what happens with invalid IDs in a batch (partial failure vs. error) or that IDs typically come from `aukro_search_offers`.

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 all six parameters are already documented, which sets the baseline at 3. The description reinforces the batch cap ('up to 20 fetched concurrently') but does not explain the currency override, HTML description toggle, or international-shipping 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?

The description opens with a specific verb and resource ('Fetch complete details for ... Aukro.cz offers') and explicitly covers both the single `offerId` and batch `offerIds` modes plus the active/archived scope. It does not, however, contrast itself with nearby siblings such as `aukro_get_offers_status_batch` or `aukro_search_offers`, so an agent must infer the routing.

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 only implied: an agent can infer this is the detail-fetch step after getting IDs from search, and the batch note hints at bulk use. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. use search to find IDs, use status_batch for lightweight status checks).

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