Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_sitemap_urls

Retrieve Brooklinen sitemap entries by type and limit, returning URL, handle, lastmod, changefreq, and available image data for crawling or monitoring.

Instructions

List Brooklinen sitemap URLs. Lists URL entries from Brooklinen'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, type, handle, lastmod, changefreq and, where present, images with caption and title.

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.7/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 burden, and it does disclose meaningful behavior: the default filter (type=all), the limit default of 50 and its hard ceiling of 250, and the per-entry return shape including loc, type, handle, lastmod, changefreq and conditional images with caption/title. It omits pagination behavior beyond the 250 cap and any auth or rate-limit notes.

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?

Two sentences, front-loaded with the core action, and the second sentence packs the filtering, capping and return-shape details without filler. The long enumerated second sentence is dense but every clause carries information.

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?

With no output schema, the description responsibly describes the returned fields, and it covers both optional parameters including defaults and ceilings. The remaining gap is the relationship to the sibling sitemap-listing tool and any pagination beyond the 250-entry cap.

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 parameters; the description's restatement of the enum values and the 50/250 limits duplicates rather than extends that. The baseline 3 applies, as the description adds almost no parameter syntax or nuance beyond the schema.

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?

The description gives a specific verb and resource ("List Brooklinen sitemap URLs") and immediately scopes it to URL entries drawn from Brooklinen's sitemaps, so an agent knows this returns URLs rather than sitemap documents. It does not, however, explicitly distinguish itself from the sibling brooklinen_sitemaps tool, leaving the boundary to inference.

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 only implied: the filtering choices (by type, capped by limit) suggest a browsing/enumeration use case, but there is no explicit when-to-use guidance or mention of the sibling brooklinen_sitemaps as the alternative for discovering the sitemaps themselves. An agent must infer the routing.

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