Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

allbirds_collections

Fetch paginated Allbirds storefront collections as normalized JSON, using page and limit parameters to browse product groupings.

Instructions

List Allbirds collections. Returns normalized collections from Allbirds (https://www.allbirds.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and adds useful behavior: results are normalized, the storefront URL is fixed server-side, and valid empty pages return 200 with an empty array. It still doesn't describe failure modes, rate limits, or return-shape details, but the disclosed edge case is valuable.

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, with the action front-loaded and no filler. The URL/normalization note and empty-page edge case each earn their place.

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 optional-pagination list tool, the description covers source, normalization, and an edge-case response. It doesn't enumerate the fields inside each collection, but that is not necessary to select or invoke the tool correctly.

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?

The input schema already documents both page and limit with defaults and max at 100% coverage, so the description doesn't need to repeat them. It adds the note that the storefront URL is fixed server-side, which clarifies why no source/URL parameter is offered.

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 first sentence, 'List Allbirds collections,' gives a specific verb and resource, and 'collections' clearly separates it from product-level siblings like allbirds_products/allbirds_collection_products. It doesn't explicitly name a sibling or scope boundary, so it stops short of the strongest differentiation.

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?

There is no explicit when-to-use or alternative guidance. The first sentence implies the tool is for fetching the Allbirds collection list, but it doesn't say when to choose this over allbirds_collection_products or allbirds_pages.

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