Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_sitemaps

List Brooklinen's child sitemaps and their types to choose the correct sitemap URL for products, collections, pages, blogs, or other data.

Instructions

List Brooklinen sitemaps. Lists the child sitemaps that Brooklinen publishes, with no parameters. Each entry has its loc URL and a type of products, collections, pages, blogs, agentic_discovery or other, which tells you which sitemap to pass to the sitemap URL endpoint.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.5/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 that the call takes no parameters (a read-only list), plus the exact return shape (`loc` and a `type`). It does not cover pagination or rate limits, but for a zero-param read tool this is solid disclosure.

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?

Three tight sentences, front-loaded with the action, then the no-parameter fact, then the return-value semantics. Every clause adds a distinct piece of information with no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description compensates fully: it names both returned fields and enumerates every `type` value. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so baseline 4 applies. The description correctly reinforces that no parameters are needed, adding confidence beyond the empty schema.

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 Brooklinen sitemaps') and immediately differentiates from the sibling endpoint by explaining that the returned `type` tells you which sitemap to pass to the sitemap URL endpoint. An agent can distinguish this from brooklinen_sitemap_urls without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly implies usage: this is the discovery step whose `type` value routes the agent to the sitemap URL endpoint. It provides strong contextual guidance but stops short of an explicit when-to-use/when-not statement or naming the alternative tool outright.

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