listam-mcp

search_listings

Read-only

Search list.am classifieds by query, category, region, and price to find matching listings in Armenia. Fetch multiple pages, return full details, and exclude agency ads for focused results.

Instructions

Search list.am listings in any category.

Price filters are applied locally to the fetched pages using approximate exchange rates, so fetch more pages when filtering heavily.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`full`	No	Return every field (images, seller badges, raw card text) instead of compact rows.
`page`	No	Result page to start from (only with category_id).
`limit`	No	Max listings to return.
`query`	No	Free-text search, e.g. 'iphone 15' or 'toyota camry'.
`currency`	No	Currency of price_min/price_max: AMD, USD, EUR or RUB.	AMD
`max_pages`	No	How many result pages to fetch (each ~1.5s).
`price_max`	No	Maximum price in `currency`.
`price_min`	No	Minimum price in `currency`.
`region_id`	No	list.am location ID. Yerevan districts: {'Ajapnyak': 2, 'Arabkir': 3, 'Avan': 4, 'Davtashen': 5, 'Erebuni': 6, 'Kanaker-Zeytun': 7, 'Kentron': 8, 'Malatia-Sebastia': 9, 'Nor Nork': 10, 'Nork-Marash': 11, 'Nubarashen': 12, 'Shengavit': 13}.
`category_id`	No	list.am category ID from list_categories. Omit to search all categories.
`extra_params`	No	Raw list.am URL query params. See get_filters for a category's own filters.
`exclude_agencies`	No	Drop ads marked as posted by an agency.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description goes beyond that by disclosing that price filters are applied locally with approximate exchange rates — a non-obvious behavioral trait that explains result imperfection and motivates max_pages tuning.

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 tight sentences, purpose front-loaded, followed immediately by the one caveat that changes how an agent should call it. No filler.

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?

An output schema exists, so return values need no explanation, and all params are documented in the schema. The description covers the key non-obvious behavior; only sibling routing is missing for a 12-param open-world search tool.

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 the schema already documents all twelve parameters thoroughly. The description reinforces the price_min/price_max semantics by explaining local application and approximate rates, but adds no format or syntax detail. Baseline 3 applies.

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?

States a specific verb and resource ('Search list.am listings') plus scope ('in any category'), so the agent knows exactly what it does. However, it never distinguishes itself from the sibling get_listings or search_by_url, which an agent facing nine sibling tools would need.

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?

It implies when to use it via the note about fetching more pages when filtering heavily, which is actionable operational advice. But there is no explicit when-not guidance or any routing to alternatives such as search_by_url or get_filters.

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

Deploy Server