within

Just in: new arrivals

new_arrivals

Read-onlyIdempotent

Find the newest arrivals in clothing, shoes, bags and jewellery from independent luxury boutiques, filtered by designer, category, department, city or price. Reads live stock so sold-out items are excluded.

Instructions

The newest clothes, shoes, bags and jewellery to arrive at independent luxury boutiques, newest first, each with its price, the sizes in stock, the shop that has it and the shopwithin.co page to buy it. Use this when someone asks what is new, what just came in or just dropped, or wants the new arrivals from a designer, in a category, for women or men, at one boutique or in one city. It reads live stock, so an item that sold out is not in the answer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "new_arrivals"
  }
}

Input Schema

Name	Required	Description
`city`	No	The city the boutiques are in, e.g. 'Toronto': a place to shop, not the shopper's own location.
`limit`	No	Items per page, default 12.
`offset`	No	Items to skip; use next_offset from the page before.
`boutiques`	No	Boutique domains to read, as shown on boutiques and items (e.g. 'wdlt117.myshopify.com').
`designers`	No	Designer or brand names, as they appear in results: 'Rick Owens', 'Chrome Hearts'.
`price_max`	No	Highest price to include, in the boutique's currency.
`categories`	No	Kinds of item, e.g. 'Sneakers', 'Jackets', 'Bags'; take values from a search result's facets.
`department`	No	Only women's or only men's.

Output Schema

Name	Required	Description	Default
`note`	Yes
`total`	Yes
`pieces`	Yes
`view_url`	Yes
`next_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value with 'It reads live stock, so an item that sold out is not in the answer,' which prevents the agent from treating results as a static catalog, and the 'newest first' ordering is useful. It stops short of describing pagination behavior, despite offset/limit existing.

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?

Two sentences, front-loaded with what the tool returns and followed by when to reach for it; there is no filler or repetition. The product-category list in the first sentence is slightly padded, but it doubles as a scope statement, so it largely earns its place.

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?

Eight optional parameters, an output schema and full annotations are all present, and the description still covers the essentials: what comes back, ordering, liveness of stock, and the intent triggers. Nothing an agent needs in order to select and call this correctly is missing.

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% and every parameter carries a clear field description, so the schema does the heavy lifting and the baseline is 3. The description's enumeration of designer, category, department, boutique and city reinforces intent-to-parameter mapping but adds no syntax, formatting, or edge-case detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a concrete verb-and-resource statement ('The newest clothes, shoes, bags and jewellery to arrive at independent luxury boutiques, newest first') and enumerates the payload fields, so the agent knows exactly what it returns. It implicitly separates itself from catalog-wide search by its 'newest first' newness framing, but never names a sibling tool, leaving differentiation to inference.

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?

Explicitly lists triggering intents: 'what is new, what just came in or just dropped,' plus the supported narrowing dimensions (designer, category, women/men, boutique, city). It gives no when-not guidance and names no alternative tool for broader or historical searching, so the agent must infer that distinction itself.

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