Skip to main content
Glama

search_ads

Search classified ads on Bazos.cz, Bazos.sk, Bazos.at, or Bazos.pl using filters like query, price range, section, and sort order. Retrieve paginated results with optional location-based sorting.

Instructions

Search ads on Bazos.cz, Bazos.sk, Bazos.at, or Bazos.pl. Returns a list of ads matching the criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort type. Available: date, price_asc, price_desc, distance. For distance, provide latitude and longitude.
limitNoLimit for pagination. Default: 20. Must be a multiple of 20 up to 200.
queryNoSearch query string
domainYesDomain to search: cz, sk, at, or pl
offsetNoOffset for pagination. Default: 0. Must be a multiple of 20.
sectionNoSection code. Available: AU = Auto DE = Deti DU = Dum a Zahrada EL = Elektro FO = Foto HU = Hudba KN = Knihy MO = Mobily MT = Motorky NA = Nabytek OB = Obleceni PC = PC PR = Prace RE = Reality SL = Sluzby SP = Sport ST = Stroje VS = Vstupenky ZV = Zvirata OS = Ostatni
latitudeNoLatitude (required when sort is distance)
price_toNoMaximum price
longitudeNoLongitude (required when sort is distance)
price_fromNoMinimum price
Behavior3/5

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

With no annotations provided, the description carries full burden but only states basic behavior (returns list of ads). It lacks details on pagination, sort behavior, error handling, or rate limits. Schema parameters hint at pagination and sorting but description does not clarify.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the purpose and scope. No wasted words, efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the parameter count (10) and no output schema or annotations, the description is minimal. It explains the general behavior but lacks details on return values, pagination behavior, and how to use parameters effectively. Adequate but incomplete for complex usage.

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 100% with descriptions for all 10 parameters. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool searches ads on specific domains (Bazos.cz, .sk, .at, .pl) and returns a list of matching ads. It distinguishes itself from siblings (get_ad_detail, get_user_ratings) by focusing on search across multiple domains.

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 usage for searching ads but provides no explicit guidance on when to use this tool versus alternatives like get_ad_detail or get_user_ratings. No exclusion criteria or context for choosing between tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/andrijdavid/bazos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server