shopino-mcp

Overview Schema Source Related Servers Discussions Admin

Browse a category, shop, tag or listing

sh_browse

Read-onlyIdempotent

Browse fashion products by category, shop, tag, or listing. Sort by price, newest, or discount, and filter by size, price range, city, or stock.

Instructions

List products of a category, a shop, a product tag or a curated listing, with sorting, price range and filters.

Use for "cheapest women's manteau in size L under 2,000,000 Toman", "newest products of shop X", "biggest discounts in bags" (discounted_only + biggest_discount). With no category / shop / tag / listing it browses all shops (e.g. today's discounts). Ids: sh_categories, sh_shops, sh_brands; size values: sh_filters. Details of a product: sh_product. More results: pass next_cursor back as cursor with the same other arguments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No	Product tag slug from sh_product `tags`, e.g. 'مانتو-بلند-مشکی-زنانه'. Only sort, in_stock_only and discounted_only apply.
`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 (a tag always gives 16 per page).
`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).
`listing`	No	Curated listing slug from sh_campaign tabs, e.g. 'پیراهن-مردانه'. Only sort, in_stock_only and discounted_only apply.
`shop_id`	No	List one shop's products (id from sh_shops / sh_shop), e.g. 489.
`brand_id`	No	Brand id from sh_brands(shop_id=...) (watch brands), e.g. 12 (Tommy Hilfiger).
`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 readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: pagination via next_cursor with identical other arguments, and the fact that an unfiltered call spans all shops. It does not discuss result volume, ranking caveats, or rate behavior, so it is strong but not exhaustive.

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?

Dense but front-loaded: purpose first, then example invocations, then fallback behavior, then id lookups, then routing, then pagination. No filler sentences; the telegraphic style is appropriate for a high-parameter browse 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?

An output schema exists, so return values need not be explained, and all 15 parameters carry schema descriptions. Combined with the description's coverage of pagination, defaults, id provenance and sibling routing, an agent has everything needed to call this 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 every parameter is already documented in the schema, including id sources, size systems and filter applicability per tag/listing. The description restates id sources and notes the discounted_only + biggest_discount combination, which is marginal added value over structured fields. 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?

Opens with a specific verb (List) and enumerates the exact resources it browses (category, shop, tag, curated listing), plus sorting/price/filter scope. It is immediately distinguishable from sh_search (query-driven) and sh_product (single-item details), both of which are named.

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?

Gives concrete when-to-use examples ('cheapest women's manteau in size L under 2,000,000 Toman', 'biggest discounts in bags'), states the no-filter fallback behavior (browses all shops, e.g. today's discounts), and routes to siblings for ids (sh_categories, sh_shops, sh_brands, sh_filters) and for details (sh_product). Alternatives and conditions are explicit.

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

Deploy Server