Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kyliecosmetics_search_suggest

Retrieve Kylie Cosmetics predictive search suggestions by query, returning matching products, collections, and search terms for storefront discovery.

Instructions

Get Kylie Cosmetics search suggestions. Returns products, collections, and query suggestions from Kylie Cosmetics's (https://www.kyliecosmetics.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses useful context ('predictive search', the three returned entity types, and that the storefront URL is fixed server-side so the caller cannot target another store), but does not state whether the call is read-only, whether results are cached or rate-limited, or how many calls are safe.

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?

Three short sentences with the core purpose front-loaded and no filler. Slightly more verbose than strictly needed, but nothing is wasted.

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 simple read-only autocomplete tool with a fully documented 3-parameter schema and no output schema, the description covers purpose, return categories, and the server-side URL constraint. The main gap is the absence of routing guidance relative to sibling tools.

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 q, limit (default 10, max 20) and types (product, collection, query). The description's enumeration of the three suggestion categories loosely maps to the types parameter but adds no format or syntax detail beyond the schema; 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 ('Get ... search suggestions') and enumerates the return categories (products, collections, query suggestions). It is clear what the tool does, but it does not distinguish this from the many sibling *_search_suggest tools across other storefronts, so the differentiation component is missing.

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

Usage Guidelines2/5

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

No guidance on when to use this versus kyliecosmetics_products, kyliecosmetics_collections, or a full search. The description implies it is an autocomplete-style endpoint but never says so or names any alternative or precondition.

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