Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_sitemap_urls

List Brooklinen sitemap URLs by type (products, collections, pages, blogs, and more), with an optional limit up to 250 entries. Use it to gather storefront URLs for crawling or indexing.

Instructions

List Brooklinen sitemap URLs. Returns capped URL entries from Brooklinen's (https://www.brooklinen.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.6/5.0
Behavior3/5

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

Annotations are absent, so the description must carry the behavioral disclosure burden. It does add some context: 'Returns capped URL entries' and 'storefront URL is fixed server-side.' However, it does not mention rate limits, pagination, error behavior, or whether it is read-only. The safety profile is not disclosed, so this is only partial transparency.

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?

The description is two sentences with zero redundant content. It front-loads the action, then provides the key constraint (capped, type matching) and a fixed behavioral note. Every sentence adds value and there is no filler.

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, low-complexity tool with two optional parameters and no output schema, the description covers the essential return information ('Returns capped URL entries') and the source context (child sitemaps). It does not explain the exact response format (e.g., array of strings) but this is acceptable given the tool's simplicity and the schema already defines parameter constraints.

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% for both parameters (type enumerates allowed values, limit states default and max). The description adds no additional meaning beyond the schema; it only restates 'matching the requested type' which is already in the type parameter description. With perfect schema coverage, the baseline 3 is appropriate.

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 specific verb ('List'), a specific resource ('Brooklinen sitemap URLs'), and a distinguishing scope ('child sitemaps matching the requested type'). It clearly differentiates from sibling tools like brooklinen_products or brooklinen_sitemaps by focusing on URL listing, and the enum parameter further clarifies the types.

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?

The description gives no explicit guidance about when to use this tool versus alternatives. It does not mention any exclusions or specific contexts where this should be preferred over sibling sitemap tools (e.g., brooklinen_sitemaps). The only implicit hint is 'matching the requested type', but it never names alternative tools or conditions for choosing them.

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