Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

kyliecosmetics_collections

List Kylie Cosmetics collections with pagination and structured JSON results. Set page and limit to browse collections or verify empty result pages.

Instructions

List Kylie Cosmetics collections. Returns collections from Kylie Cosmetics (https://www.kyliecosmetics.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.4/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 disclosure burden and does add real behavioral detail: the storefront URL is fixed server-side (no host parameter is expected) and empty trailing pages return 200 with an empty array rather than an error. That edge-case semantics is exactly the kind of thing the schema cannot convey. It omits pagination termination guidance and whether ordering is stable.

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, purpose front-loaded, no filler. The parenthetical URL repeat of 'Kylie Cosmetics' is mildly redundant but not wasteful enough to penalize further.

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?

For a two-parameter, paginated listing tool with full schema coverage and no output schema, the essential call mechanics are covered. However, it never indicates what a returned collection object contains (id/handle/title), which matters because the natural follow-up call, kyliecosmetics_collection_products, needs a collection identifier the agent would have to guess.

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% — page ('1-based, defaults to 1') and limit ('defaults to 50, up to 250') are already fully documented in the schema. The description adds nothing about either parameter, so the 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 ('List Kylie Cosmetics collections') and pins the source storefront, so the agent knows exactly what comes back. It never names or contrasts with the sibling it is most likely to be confused with (kyliecosmetics_collection_products), so it stops short of full differentiation.

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?

There is no statement of when to use this tool versus kyliecosmetics_collection_products, kyliecosmetics_products, or kyliecosmetics_page. The agent must infer from the name that this enumerates collections rather than the products inside them; no prerequisites or exclusions are given.

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