Skip to main content
Glama

Unegui.mn 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 mn. Default mn.
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

C2.9/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 — results never include seller contacts — but says nothing about pagination via page_token/next_page_token or result limits (maximum 30), which matter for a search tool.

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. It is efficient, though the brevity borders on under-specification rather than optimal conciseness.

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 search tool, the description omits filtering, sorting, price bounds, and pagination behavior, leaving the agent to infer usage from the schema alone. The output schema and annotations cover return shape and safety, but the invocation picture is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 60% schema description coverage with ten parameters, the description adds no parameter meaning at all — no mention of query, filters, price range, ordering, or paging. limit, ordering, price_min and price_max are undocumented in both the schema and the description, so the description fails to compensate for the coverage gap.

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 names a specific verb and resource ("Search listings on the marketplace"), which is clearly distinct from the single-item sibling get_advert. It does not, however, explicitly contrast itself with siblings or state what a listing is, so it stays short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention that all ten parameters are optional, and no routing to alternatives. The note that results never include seller contacts only weakly implies that reveal_contact is needed for contact details.

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