Skip to main content
Glama

Somon.tj 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 ru, tg. Default ru.
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

A3.6/5.0
Behavior4/5

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

Annotations already establish this as a read-only operation, and the description adds a genuine behavioral fact beyond them: returned listings never contain seller contacts, which sets expectations for the response contents. It says nothing about pagination behavior or result-set size limits, but the output schema covers the return shape.

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 short sentences with the core action front-loaded and no filler. Given the tool has ten parameters and pagination, however, the brevity edges toward under-specification rather than efficient density.

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?

For a ten-parameter, paginated search tool, the description omits the default page size, how page_token chaining works, ordering defaults, and the ru/tg language default. The output schema offsets some of this, but the pagination and filtering workflow is not fully covered anywhere in the description.

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?

The description provides no parameter-level meaning at all. Schema coverage is 60% and the documented fields (query, language, attributes, page_token, category_id) already carry their own explanations, so the baseline of 3 applies; the four undocumented fields (limit, ordering, price_min, price_max) are largely self-describing.

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 gives a specific verb and resource ("Search listings on the marketplace"), which is clearer than the tool name alone. It stops short of distinguishing this from siblings such as get_advert or list_categories, so an agent must infer that this is the multi-result query path.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named. The clause "Results never include seller contacts" implicitly signals that a separate contact-reveal step is needed, but the agent must connect that to reveal_contact itself.

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