Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

sephora_category

Fetch one page of a Sephora category or browse listing by slug, with sort options and facet filters for brand, price, rating, and product attributes.

Instructions

Sephora category browse. Returns one page of a Sephora category/browse listing (e.g. Makeup, Skincare), with the same sort and facet filters as /sephora/search. slug is the path segment after sephora.com/shop/, e.g. makeup-cosmetics. The response uses Sephora's public catalog search to keep browse listings available when the category page's legacy embedded data is absent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "sephora_category"
  }
}

Input Schema

Name	Required	Description
`page`	No	Result page, 1-based, defaults to 1
`slug`	Yes	Category-page slug
`brand`	No	One or more exact brand names to filter to (OR'd together); repeat the param for multiple values
`filter`	No	Additional facet:value filters, repeat the param for multiple; facet must be one of: benefits, ingredientpreferences, colorfamily, formulation, size, shoppingpreferences, agerange, skintype, finish, skinconcerns, coverage, hairtype, hairconcerns, hairtexture
`is_new`	No	When true, filters to products flagged New
`sort_by`	No	Sort order, defaults to featured
`price_max`	No	Maximum price in whole dollars; must be set together with price_min
`price_min`	No	Minimum price in whole dollars; must be set together with price_max
`rating_min`	No	Minimum star rating, 1 to 4

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.5Sep 26, 2026

addedInput schema / properties / brand / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / filter / items
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / sort_by / enum

Added value: +[
+  "featured",
+  "top_rated",
+  "new",
+  "best_selling",
+  "price_low_to_high",
+  "price_high_to_low"
+]

Addedv1.14.0Aug 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that it returns one page and uses a public catalog search fallback when legacy data is absent, which is useful behavioral context. However, it omits details like pagination limit, response structure, or error behavior. The fallback explanation adds value beyond a simple 'returns browse pages.'

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?

Three sentences, no fluff, and the primary purpose is front-loaded. Every sentence adds value: purpose, slug explanation, and fallback behavior. The structure is effective for an agent to quickly grasp the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essentials for a category browse tool: what it returns, how to specify the category, and a note on fallback behavior. However, without an output schema, the description does not describe the response fields, pagination metadata, or any error conditions. For a tool with 9 parameters, this is adequate but not comprehensive.

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 description coverage is 100%, so baseline is 3. The description adds meaningful guidance for the critical slug parameter by explaining it is the path segment after sephora.com/shop/ with an example. It also connects filter parameters to the same set as /sephora/search, providing context beyond the schema. This justifies a 4.

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?

States a specific verb and resource: 'Returns one page of a Sephora category/browse listing.' It is clear what the tool does, but it does not explicitly distinguish itself from siblings like sephora_search or sephora_categories. The mention of 'same sort and facet filters as /sephora/search' hints at relationship but does not name alternatives.

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

Usage Guidelines3/5

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

Provides some context by explaining the slug format and that it shares filters with search, but does not explicitly state when to prefer this over search or categories. No exclusions or alternative tool names are given, leaving the agent to infer usage from the context.

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

Deploy Server