Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

allbirds_sitemap_urls

Fetch Allbirds sitemap URLs by type and limit, returning structured loc, type, handle, lastmod, changefreq, and optional image data.

Instructions

List Allbirds sitemap URLs. Lists URL entries from the Allbirds store sitemaps, filtered by type (all, products, collections, pages, blogs, agentic_discovery or other; default all). limit defaults to 50 and is capped at 250. Each entry has loc, type, handle, lastmod, changefreq and optional images.

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but for a read-only list operation there is little safety behavior to disclose. It does add useful operational context: the limit default of 50 and the hard cap of 250, plus the shape of each returned entry (loc, type, handle, lastmod, changefreq, images). It stops short of stating pagination behavior 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?

Purpose is front-loaded in the first sentence, followed by filter semantics and return shape. No filler, and the sentences each carry information, though the type enumeration is partially redundant with the schema.

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?

There is no output schema, so the description's disclosure of entry fields is genuinely necessary and supplied. Combined with the type/limit semantics, an agent has enough to call and interpret the tool, though the lack of guidance distinguishing it from sibling sitemap tools is a gap.

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 both parameters are already fully documented in the schema. The description largely restates the same enum values, default, and cap without adding syntax or filtering semantics beyond what the structured schema provides.

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?

States a specific verb (List) and resource (Allbirds sitemap URL entries), and specifies that these are entries from the store sitemaps filtered by type. It is clear what the tool returns, though it never explicitly contrasts itself with the sibling allbirds_sitemaps, so the agent must infer the scope difference.

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?

No when-to-use guidance is given other than the type filter enumeration. There is no indication of when an agent should prefer this over allbirds_sitemaps, allbirds_products, or allbirds_collections, leaving the routing decision to inference.

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