Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

allbirds_sitemaps

Lists the child sitemaps in the Allbirds store's sitemap index with each loc and type (products, collections, pages, blogs, other). Use the types to filter URL retrieval.

Instructions

List Allbirds sitemaps. Lists the child sitemaps in the Allbirds store's sitemap index, each with its loc and a type of products, collections, pages, blogs, agentic_discovery or other. Takes no parameters. The types match the type filter of allbirds-sitemap-urls.

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?

With no annotations, the description carries the behavioral burden and does well: it discloses that the operation is a listing, describes the return shape (`loc` and `type`), and enumerates the exact type values. It does not mention authentication, rate limits, or pagination, but for a parameterless sitemap index those omissions are minor.

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 short sentences, front-loaded with the action and resource. Every sentence adds useful information: scope, return structure, type values, parameterlessness, and the relationship to the sibling filter.

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?

Given a zero-parameter list tool with no output schema and no annotations, the description is complete enough: it explains what is listed, what each item contains, and the allowed type values. An agent has everything needed to call it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description explicitly says 'Takes no parameters,' which fully matches the empty schema and leaves no ambiguity for the agent.

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 Allbirds sitemaps') and immediately scopes it as the child sitemaps in the store's sitemap index. It names the output fields and enumerates the possible `type` values, so an agent can distinguish it from the URL-fetching sibling.

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?

The description gives clear usage context by saying it takes no parameters and that its `type` values match the `type` filter of `allbirds-sitemap-urls`. It implies this is the discovery step before fetching URLs, but it does not explicitly state when not to use it or spell out the alternative workflow.

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