minxa

Search minxa fashion

search_fashion_products

Read-onlyIdempotent

Search minxa, a fashion search engine, for clothes, shoes, bags, jewelry, accessories and beauty products across a broad selection of popular online shops at every price point. Describe what the person wants in plain words, in any language: the occasion, place, weather, look or budget is enough, e.g. 'something to wear to a beach wedding in Mexico' with max_price_usd 200. Returns up to 10 products with photo, price (in the shop's currency), brand, shop and a link to each product's page on minxa.com, plus a link to all results on minxa.com. minxa covers clothes, shoes, bags, jewelry, accessories and beauty products only, so do not call it for anything else.

Input Schema

Name	Required	Description	Default
`limit`	No	How many products to return (1-10).
`query`	Yes	What the person wants, in plain words and in any language: the item itself, or the occasion, place, weather, look and budget it is for (e.g. 'something to wear to a beach wedding in Mexico'), plus any colour, material or brand.
`gender`	No	Whose clothes: women (minxa's default), men, or girls / boys for kids. Set it from the request: "men's linen shirts" is men, "something for my daughter" is girls; leave it out when the request doesn't say whose. Left out, minxa searches women's unless the words say whose, as minxa.com does; the answer's gender is the one searched.	women
`max_price_usd`	No	Highest price in US dollars. When set, items the shop prices in another currency are left out.

Output Schema

Name	Required	Description
`items`	Yes
`query`	Yes
`gender`	Yes
`fallback`	No	Present only when the full search was busy and these are the newest items in the category the query names.
`no_match`	No	Present only when nothing minxa has matches the request: it is not a fashion or beauty product.
`disclosure`	Yes	How minxa is paid (null when nothing matched).
`max_price_usd`	Yes
`total_matches`	Yes	Cards minxa.com shows for this search (each colour is a card).
`minxa_search_url`	Yes	All results for this search on minxa.com (null when nothing matched).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / query / description

Previous value: -"What the person wants, in plain words and in any language: the item, colour, material, style, occasion, brand."New value: +"What the person wants, in plain words and in any language: the item itself, or the occasion, place, weather, look and budget it is for (e.g. 'something to wear to a beach wedding in Mexico'), plus any colour, material or brand."

Changed9 schema fields changedOct 13, 2026

changedInput schema / properties / gender / description

Previous value: -"Whose clothes: women (minxa's default), men, or girls / boys for kids. Set it from the request: \"men's linen shirts\" is men, \"something for my daughter\" is girls; leave it out when the request doesn't say whose."New value: +"Whose clothes: women (minxa's default), men, or girls / boys for kids. Set it from the request: \"men's linen shirts\" is men, \"something for my daughter\" is girls; leave it out when the request doesn't say whose. Left out, minxa searches women's unless the words say whose, as minxa.com does; the answer's gender is the one searched."

changedInput schema / properties / query / description

Previous value: -"What the person wants, in plain words: the item, colour, material, style, occasion, brand."New value: +"What the person wants, in plain words and in any language: the item, colour, material, style, occasion, brand."

addedOutput schema / properties / disclosure / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / disclosure / description

Previous value: -"How minxa is paid."New value: +"How minxa is paid (null when nothing matched)."

removedOutput schema / properties / disclosure / type
```
Removed value: -"string"
```

addedOutput schema / properties / minxa_search_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / minxa_search_url / description

Previous value: -"All results for this search on minxa.com."New value: +"All results for this search on minxa.com (null when nothing matched)."

removedOutput schema / properties / minxa_search_url / type
```
Removed value: -"string"
```

addedOutput schema / properties / no_match

Added value: +{
+  "description": "Present only when nothing minxa has matches the request: it is not a fashion or beauty product.",
+  "enum": [
+    "outside_fashion_beauty"
+  ],
+  "type": "string"
+}

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: return count cap (up to 10) and, notably, the non-obvious rule that setting max_price_usd drops items priced in other currencies, plus the gender defaulting behavior.

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?

Front-loaded with scope, then guidance, then return format, then the exclusion — a sensible order. Slightly verbose: the product-category list is repeated verbatim in the first and last sentences, which is redundant but not harmful.

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 documented, yet the description still summarizes the payload (photo, price, brand, shop, product link). Combined with usage examples, exclusions, and the currency caveat, an agent has everything needed to invoke this correctly.

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. The description goes further by demonstrating how query and max_price_usd combine in a real call and by explaining the gender default semantics ('left out, minxa searches women's unless the words say whose'), which clarifies intent rather than restating the schema.

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?

States a specific verb (Search) and resource (minxa fashion search engine) and enumerates the exact catalog scope: clothes, shoes, bags, jewelry, accessories, beauty. The closing sentence explicitly bounds the domain, so an agent knows precisely what this tool does and does not cover.

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 explicit when-to-use guidance with a concrete example ('something to wear to a beach wedding in Mexico' with max_price_usd 200) and an explicit when-not-to-use exclusion ('minxa covers ... only, so do not call it for anything else'). No siblings exist, so no alternative routing is needed.

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

All minxa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?