Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ulta_search

Search Ulta Beauty products by keyword to return paginated results 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 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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses real page-based pagination and, notably, that nonsense keywords and out-of-range pages return genuine empty results rather than fallbacks or errors. It omits auth/permission needs and any rate-limit context, keeping it from a 5.

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?

Four short sentences, front-loaded with purpose, then pagination, return contents, and edge-case behavior. Every sentence carries information an agent needs, and there is no padding.

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?

There is no output schema, and the description compensates by naming the returned fields (brand, pricing, rating, review count) and covering empty-result edge cases. Missing only secondary details like total result counts or pagination limits, which is minor for this 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?

Schema description coverage is 100%, so the schema already documents both query and page. The description reinforces pagination semantics ('real page-based pagination') but adds no syntax or format detail beyond the schema's 'Result page, 1-based, defaults to 1.' Baseline 3 applies.

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: 'Search Ulta Beauty products ... by keyword.' An agent can tell this is a keyword catalog search rather than a detail or category fetch. It does not explicitly distinguish itself from close siblings such as ulta_suggest or ulta_product, so it stops short of a 5.

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 is implied by 'Searches Ulta Beauty's product catalog by keyword,' which signals keyword-driven lookup, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., ulta_suggest for autocomplete). The remaining sentences describe behavior, not selection criteria.

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