Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

everlane_sitemap_urls

Lists Everlane sitemap URLs filtered by type and limit, returning loc, inferred type, handle, last modified date, change frequency, and image metadata for SEO or crawl planning.

Instructions

List Everlane sitemap URLs. Lists URL entries from Everlane's sitemaps, filtered by type (all by default, or products, collections, pages, blogs, agentic_discovery, other) and capped by limit (default 50, max 250). Each entry has its loc, inferred type, handle, last modified date, change frequency, and images with caption and title when present.

Input 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.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return shape in detail (loc, inferred type, handle, last modified date, change frequency, images with caption/title), which is genuinely useful since no output schema exists. It does not, however, mention pagination, auth requirements, or rate limits.

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 front-loaded sentences that stay on topic. Minor redundancy between "List Everlane sitemap URLs" and "Lists URL entries from Everlane's sitemaps," but nothing wasteful.

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-optional-param tool with no output schema, the description supplies parameter defaults and a full field-level picture of each returned entry, which is what an agent needs to call it correctly. Only pagination behavior and safety profile are unaddressed.

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% and both parameters are already documented there. The description restates the enum values and the limit default/max, adding no meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("List Everlane sitemap URLs / URL entries from Everlane's sitemaps") and distinguishes this from roles like everlane_sitemaps or everlane_products. An agent can identify exactly what this returns without opening the schema.

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?

Explains the `type` and `limit` filtering, which implies when to reach for this tool (bulk URL enumeration by category), but never states when to use it versus siblings such as everlane_sitemaps or everlane_products. Usage is implied rather than directed.

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