Skip to main content
Glama

JaCars classifieds

Search listings

search_adverts
Read-only

Search listings on the marketplace. Results never include seller contacts.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFree-text search, e.g. 'iphone 15 128gb'.
languageNoLanguage of listing texts: one of en. Default en.
locationNoCity or district name.
orderingNo
price_maxNo
price_minNo
attributesNoCategory filters from get_category_filters: {key: value} for select, {key: [values]} for multiselect, {key + '_min' / key + '_max': number} for range.
page_tokenNonext_page_token of the previous result, same filters.
category_idNoCategory from list_categories.

Output Schema

NameRequiredDescriptionDefault
pageYes
totalNoMatching listings, may be capped by the site.
advertsYes
locationNoLocation the search was narrowed to.
next_page_tokenNoPass to search_adverts for more results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that seller contacts are stripped from results — but says nothing about result volume, pagination behavior beyond the schema's page_token, or rate limits on an external marketplace.

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?

Two compact sentences with the primary purpose front-loaded and no filler. It is arguably too terse for a ten-parameter search tool, but nothing written is wasteful.

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

Completeness2/5

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

For a ten-parameter, open-ended marketplace search, the description omits the discovery workflow (use list_categories for category_id, get_category_filters for attributes), pagination expectations, and ordering semantics. The output schema and annotations cover returns and safety, but the invocation guidance an agent needs is largely absent.

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 60% (query, language, location, attributes, page_token, category_id documented; limit, ordering, price_min, price_max only titled), and the description contributes nothing about any parameter. With partial coverage and no compensating explanation, this sits at the minimum-viable level rather than adding value.

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?

"Search listings on the marketplace" is a clear verb+resource pair, and the added note that results never include seller contacts implicitly distinguishes it from reveal_contact. It stops short of naming any sibling outright, so differentiation is inferred rather than stated.

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 contact-exclusion note hints that an agent needing a seller's phone number must go elsewhere (reveal_contact), which is real but indirect routing guidance. There is no explicit statement of when to use this versus get_advert, nor of the list_categories/get_category_filters prerequisite workflow that the schema parameters imply.

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