shopino-mcp

Overview Schema Source Related Servers Discussions Admin

Search products

sh_search

Read-onlyIdempotent

Search roughly 960,000 fashion products by keyword across about 10,000 Iranian shops, comparing price, discount, stock, and seller. Filter by category, shop, size, price, or city for same-day courier.

Instructions

Search products across all Shopino shops by keyword: price to pay, discount, stock and selling shop.

Use first for "price of X" / "where can I buy X". Narrow with category_id (sh_categories), shop_id, size, price range or city (same-day courier). For the cheapest matches in one flat list use sh_find_cheapest. Sizes, colors and stock per variant: sh_product. More results: pass next_cursor back as cursor (keep the other arguments the same).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Only shops with same-day courier delivery in this city, e.g. 'تهران' (list in sh_filters).
`sort`	No	Order: relevance (Shopino's ranking), cheapest / most_expensive (price to pay), newest, biggest_discount.	relevance
`limit`	No	Products per page.
`query`	Yes	Product name or keyword, Persian works best, e.g. 'مانتو کتان' or 'کفش ورزشی'.
`sizes`	No	Sizes in the chosen size_system (any of them), e.g. ['M', 'L'] or ['40'].
`cursor`	No	next_cursor of the previous reply, for the next page (keep the other arguments the same).
`shop_id`	No	Search inside one shop (id from sh_shops / sh_shop), e.g. 489.
`max_price`	No	Maximum price to pay in Toman, e.g. 2000000.
`min_price`	No	Minimum price to pay in Toman, e.g. 500000.
`category_id`	No	Category id from sh_categories, e.g. 385 (women's manteaus); includes sub-categories.
`size_system`	No	Size system for `sizes` (values in sh_filters): standard (S, M, L...), european (38, 40...), shoe, kid_shoe, pants, underwear, baby, kid; freesize = only free-size items.
`in_stock_only`	No	Only products in stock now.
`discounted_only`	No	Only discounted products.

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

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds operational context: city filter means same-day courier availability, and cursor pagination requires keeping other args constant. No safety or mutation details are contradicted, but no additional auth or rate-limit behavior is disclosed.

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?

Front-loaded with purpose then usage guidance, with no wasted sentences. Each sentence (purpose, usage, alternatives, pagination) earns its place for a complex 13-parameter tool.

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?

All structured fields are rich: 100% schema coverage, full annotations, and an output schema. The description provides routing guidance and pagination behavior, leaving return values to the output schema. Nothing critical is missing for an agent to call it correctly.

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 all 13 parameters are fully documented in the schema. The description echoes some filters (category, shop, size, price, city) but adds no new syntax or constraints beyond what the schema provides. Baseline 3 applies.

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?

Specific verb ('Search products') and resource with scope ('across all Shopino shops by keyword') plus what data is returned (price, discount, stock, selling shop). It also distinguishes itself from sh_find_cheapest and sh_product, so an agent can route correctly.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use this first for price/buy queries, names filters to narrow results, and directs to alternatives for cheapest matches (sh_find_cheapest) and variant details (sh_product). It also explains pagination via cursor, covering when to use, when not to, and alternatives.

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

Deploy Server