Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kyliecosmetics_sitemap_urls

Return capped Kylie Cosmetics sitemap URL entries by type—including products, collections, pages, and blogs—from child sitemaps, limited per request up to 250.

Instructions

List Kylie Cosmetics sitemap URLs. Returns capped URL entries from Kylie Cosmetics's (https://www.kyliecosmetics.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSitemap type. Allowed values: all, products, collections, pages, blogs, agentic_discovery, other
limitNoMaximum URL entries, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "products",
+  "collections",
+  "pages",
+  "blogs",
+  "agentic_discovery",
+  "other"
+]
  2. Addedv1.16.0

TDQS

A3.7/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-disclosure burden. It discloses that results are capped URL entries and that the storefront URL is fixed server-side. However, it does not clarify what happens when 'type' is omitted, and it doesn't describe the response container or pagination behavior.

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?

Two sentences with no filler. The main action and scope are front-loaded, and both sentences earn their place: one defines what is returned, the other clarifies that the domain is not a caller-supplied parameter.

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?

The tool is simple and the schema covers both parameters, but there is no output schema and no annotations. The description leaves ambiguity about the omitted-type behavior and the exact shape of the returned URL entries, so an agent may not be fully confident when calling with no arguments.

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 coverage is 100%, so the baseline of 3 applies. The description reinforces that 'type' selects a child-sitemap subset and that results are capped, but it adds no new parameter semantics. Enum values such as 'agentic_discovery' and 'other' remain unexplained.

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 clear verb and resource: 'List Kylie Cosmetics sitemap URLs' from child sitemaps. It adds distinguishing detail—'capped URL entries', 'matching the requested type', and 'storefront URL is fixed server-side'—so it is not just a restatement of the tool name.

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?

The description gives useful context about type-filtered child-sitemap URLs, but it never explicitly says when to choose this tool over kyliecosmetics_sitemaps or the product/page collection tools. No alternatives or exclusions are mentioned, so the when-to-use guidance is only implied by the enum.

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