Skip to main content
Glama

search_products

Read-onlyIdempotent

Search Ozon's product catalog with pagination, sorting, and price filters to retrieve product details, prices, ratings, and delivery dates.

Instructions

Search Ozon like the site does, with real pagination.

Walks Ozon's result pages from page until limit items are collected; pages are never cut, so next_page continues without gaps (Ozon itself may repeat an item across pages — repeats within one call are dropped). Ozon does not report a total count.

Per item: SKU, name, brand (only when the tile shows it — otherwise use get_product), price_with_ozon_card_rub (tiles show only the Ozon Card price; e-books and similar show a single price_rub), crossed-out price, Ozon's discount label, rating and review count as on the tile (usually the whole variant line's — see rating_shared_with), delivery date for the region (express_delivery = faster paid option with its surcharge_rub), units_left when Ozon shows a stock counter, sold_by_ozon, adult_only, marketing labels. resolved_to shows the category/brand filters Ozon applied to the query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOzon result page to start from (continue with `next_page`)
sortNoOrder of results, the site's optionspopular
limitNoFetch whole Ozon pages until at least this many items (pages hold 8–36)
queryYesSearch phrase, as typed on the site (Russian works best)
price_maxNoUpper bound, rubles (Ozon filters by the Ozon Card price)
price_minNoLower bound, rubles (Ozon filters by the Ozon Card price)
auto_categoryNoLet Ozon narrow the query to its predicted category/brand, as the site does; false searches every category

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds significant behavioral detail beyond that: pages are never cut, repeated items within a call are dropped, Ozon reports no total count, and many field-level caveats are disclosed (Ozon Card price only, e-books single price, rating_shared_with, conditional units_left, resolved_to filters).

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?

Although the description is long, it is densely informative with no filler. The first sentence establishes the core purpose, and the following sentences each earn their place by documenting pagination behavior, per-item field caveats, and the resolved_to detail.

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

Completeness5/5

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

This is a complex scraping/search tool with many Ozon-specific quirks, and the description covers them thoroughly: page walking, repeat deduplication, missing total count, conditional fields, delivery date, price semantics, and category/brand filters. An output schema exists, so the description does not need to repeat return-value structure; the behavioral context is complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to the pagination parameters by explaining how page, limit, and next_page interact and that Ozon pages are never cut. The tile-level price and brand caveats also enrich what the returned data means, though the description does not add much beyond the schema for sort, query, or auto_category.

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 opens with 'Search Ozon like the site does, with real pagination,' which clearly identifies the verb, resource, and mode of operation. It distinguishes itself from the sibling tools (get_product, get_reviews, compare_products) by framing this as the site-style search and by explicitly routing missing brand data to get_product.

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

Usage Guidelines4/5

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

The description gives concrete usage context: it searches Ozon result pages, accumulates until limit items, and continues via next_page without gaps. It also names an alternative explicitly ('otherwise use get_product'), but it does not provide a broader when-to-use vs. when-not-to-use comparison against get_reviews or compare_products.

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