Crawlora MCP

ulta_category

Read-only

Browse an Ulta Beauty category page's product grid, with real page-based pagination and the category's own guided-navigation refinement options. category accepts a category path or full URL copied from Ulta's own site navigation. filter narrows results using Ulta's own guided-navigation facet-code shape, comma-joined for multiple -- discover valid codes for a category from that category's own response facets field, whose value is ready to use directly as this parameter. An unrecognized category returns a not-found error.

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": {
      "category": "<category>"
    },
    "name": "ulta_category"
  }
}

Input Schema

Name	Required	Description
`page`	No	Result page, 1-based, defaults to 1
`filter`	No	Guided-navigation facet code(s), comma-joined for multiple
`category`	Yes	Ulta category path or URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / category / description
```
Added value: +"Ulta category path or URL"
```
- addedInput schema / properties / filter / description
```
Added value: +"Guided-navigation facet code(s), comma-joined for multiple"
```
- addedInput schema / properties / page / description
```
Added value: +"Result page, 1-based, defaults to 1"
```
First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: real page-based pagination and the fact that an unrecognized category yields a not-found error. It stops short of describing return shape or rate/limit behavior, but that is a reasonable boundary since an output schema exists.

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, then parameter guidance, then error behavior in a logical order. It is on the longer side and the filter sentence is dense, but essentially every sentence carries information an agent needs, so waste is minimal.

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

Completeness4/5

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

Given an output schema exists, return values need not be explained, and the description usefully cross-references the response facets field. For a read-only browse tool with three documented params, it covers purpose, inputs, pagination, and error behavior, leaving only minor gaps like result-count or sort behavior.

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 baseline is 3, but the description meaningfully exceeds the schema: it explains that category accepts either a path or a full copied URL, that filter uses Ulta's guided-navigation facet-code shape, and crucially how to obtain valid codes from the response facets field. That is actionable guidance the terse schema descriptions do not convey.

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 and resource ('Browse an Ulta Beauty category page's product grid') and scopes it further with pagination and guided-navigation refinement. This clearly differentiates it from siblings like ulta_search (keyword search) and ulta_categories (category listing) without needing to compare schemas.

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?

Usage context is implied by the browse-a-category framing, and the description gives a concrete workflow hint (pull filter codes from a category's own facets field). However, it never states when to prefer this tool over ulta_search/product for a given goal, and offers no exclusions or alternative routing.

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

All Crawlora MCP 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?