Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ulta_search

Search Ulta Beauty's product catalog by keyword, paginate through results, and return normalized products with brand, pricing, rating, and review count.

Instructions

Search Ulta Beauty products. Searches Ulta Beauty's product catalog by keyword, with real page-based pagination. Returns normalized products with brand, pricing, rating, and review count. An unrecognized/nonsense keyword returns a genuine empty result rather than a fallback set. Requesting a page beyond the available results returns a normal, empty result rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page, 1-based, defaults to 1
queryYesSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.3/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It goes beyond generic search behavior by disclosing real page-based pagination, normalized product output, genuine empty results for nonsense keywords, and empty results instead of errors for out-of-range pages. These are valuable, non-obvious behavioral traits.

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?

The description is front-loaded and efficient, with edge-case behaviors clearly stated. However, the first two sentences are slightly redundant — 'Search Ulta Beauty products' and 'Searches Ulta Beauty's product catalog by keyword' — so not every sentence earns its place fully.

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?

For a two-parameter search tool with no output schema and no annotations, the description covers the purpose, return fields, pagination behavior, and edge cases. It does not specify page size or sort order, but these are not necessary for correctly invoking the tool.

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?

The schema already covers 100% of the two parameters, including descriptions for query and page. The description reinforces 'keyword' and 'page-based pagination' but does not add meaningful new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Search Ulta Beauty products' and elaborates that it searches the catalog by keyword, returning normalized products with brand, pricing, rating, and review count. This clearly distinguishes it from sibling tools like ulta_category, ulta_product, or ulta_suggest.

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?

It clearly frames when to use the tool by specifying keyword search of Ulta Beauty's product catalog and real page-based pagination. However, it does not explicitly name or exclude alternatives such as ulta_category or ulta_product, so no when-not guidance is provided.

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

Deploy Server

Other Tools