Vitrine: Trending Fashion, Luxury, Sneakers & Design

What is trending

trending

Read-onlyIdempotent

List what is hot or rising right now, ranked by trend score (0 to 100), optionally within one category (fashion, accessories, interior), tier or gender (men and women include unisex pieces). Use it for open questions like 'what's trending in bags' or 'in menswear'; use search when the shopper has a specific need. 'hot' means confirmed by demand data, 'rising' means early momentum not yet confirmed. Returns 5 to 20 items in the same shape as search, plus meta.updated_at. Read-only. Without a key, results are capped at 5 and omit trend data and match reasons; a free key (POST https://vitrine.fashion/v1/keys, sent as 'Authorization: Bearer ') unlocks them. Rate limits: 10 calls a minute anonymous, 60 with a key. With a key, each item also carries trend_reason (why it has its trend status), trend_sources (the signals behind it: source, url, signal type, date, contribution; [] when the status comes from curation alone) and trend_review (when the status last changed and whether a human reviewer approved it).

Input Schema

Name	Required	Description
`tier`	No
`agent`	No
`limit`	No	1 to 20. Anonymous callers get at most 5.
`gender`	No	Department. 'men' returns men's and unisex pieces, 'women' returns women's and unisex pieces, 'unisex' returns unisex pieces only.
`category`	No

Output Schema

Name	Required	Description	Default
`meta`	Yes
`count`	Yes
`results`	Yes
`query_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

changedInput schema / properties / limit / description

Previous value: -"5 to 20. Anonymous callers get 5."New value: +"1 to 20. Anonymous callers get at most 5."

changedInput schema / properties / limit / minimum
```
Previous value: -5New value: +1
```

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / gender

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "women",
+        "men",
+        "unisex"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Department. 'men' returns men's and unisex pieces, 'women' returns women's and unisex pieces, 'unisex' returns unisex pieces only."
+}

addedOutput schema / properties / results / items / properties / gender

Added value: +{
+  "description": "Department. Accessories and interior are usually unisex.",
+  "enum": [
+    "women",
+    "men",
+    "unisex"
+  ],
+  "type": "string"
+}

Changed1 schema field changedNov 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "meta": {
+      "properties": {
+        "access": {
+          "enum": [
+            "full",
+            "basic"
+          ],
+          "type": "string"
+        },
+        "terms": {
+          "type": "string"
+        },
+        "upgrade": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "query_id": {
+      "type": "integer"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "availability": {
+            "enum": [
+              "in_stock",
+              "low_stock",
+              "preorder",
+              "out_of_stock"
+            ],
+            "type": "string"
+          },
+          "brand": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "image_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "outbound_url": {
+            "description": "Tracked link to the retailer's product page. Checkout happens there.",
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "trend_score": {
+            "description": "0 to 100. With a key.",
+            "type": "integer"
+          },
+          "trend_status": {
+            "description": "With a key.",
+            "enum": [
+              "hot",
+              "rising",
+              "steady",
+              "fading"
+            ],
+            "type": "string"
+          },
+          "why": {
+            "description": "One-line reason it matches. With a key.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "brand",
+          "price",
+          "currency",
+          "availability",
+          "outbound_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "results",
+    "meta"
+  ],
+  "type": "object"
+}

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only/idempotent, and the description still adds substantial context: result cardinality (5-20), the exact consequence of anonymous access (capped at 5, trend data and match reasons omitted), how to obtain a free key with the header format, and concrete rate limits (10/min anonymous, 60/min keyed). It also names the extra keyed-only fields (trend_reason, trend_sources, trend_review). Slightly long-winded, but nothing here is redundant with the annotations.

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 purpose and the sibling routing rule, with operational details trailing. It is a single dense paragraph covering auth, limits, and return enrichment — all earning their place, though the parenthetical field inventories could be tightened.

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?

Despite an output schema existing, the description still tells the agent the result shape and keyed-only fields, plus quota, auth, and pagination-equivalent caps. For a zero-required-param discovery tool with a sibling, an agent has everything needed 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 coverage is only 40%, so the description must compensate. It does explain gender semantics and the category values, but the six tier enum values (luxury_anchor, trend_brand, streetwear, sneakers, resale_vintage, accessories_interior) are never defined anywhere, and the 'agent' object's purpose is left to the schema. Partial compensation only.

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 and resource ('List what is hot or rising right now') and states the ranking basis (trend score 0-100) plus optional scoping dimensions. It is clearly distinguishable from sibling 'search' (specific-need queries) and 'trending_brands' (brands, not items).

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 routes between this tool and its alternative: 'Use it for open questions like what's trending in bags... use search when the shopper has a specific need', with two concrete example queries. The when-not condition is stated, not inferred.

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

All Vitrine: Trending Fashion, Luxury, Sneakers & Design tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?