Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

allbirds_pages

List static pages from the Allbirds store with page and limit controls, returning handles, titles, URLs, IDs, timestamps, and content for site mapping or audits.

Instructions

List Allbirds static pages. Lists static pages from the Allbirds store, paged with page (default 1) and limit (default 50, max 250). Each item has handle, title, url, id, publish and update times and plain-text content. In some responses items carry only handle, url and updated_at.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum static pages, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: pagination defaults and the 250 cap, plus the notable warning that some responses return only a reduced item shape ('handle', 'url', 'updated_at'). This variable-response disclosure is genuinely valuable. It stops short of auth or rate-limit context.

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?

Three front-loaded sentences with zero filler: purpose first, then pagination, then the item shape. Slightly dense but every sentence carries information.

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?

With no output schema and no annotations, the description compensates by enumerating the returned item fields and flagging the inconsistent shape. That covers what an agent needs for this read-only listing tool; only auth and rate-limit context are absent.

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 documented, and the description merely restates defaults and the max. Baseline 3 applies since the schema does the heavy lifting and the description adds no new parameter semantics.

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 static pages'), making clear it is a bulk listing tool. It implicitly distinguishes itself from the singular allbirds_page sibling by the plural 'pages' and the paging parameters, though it never names the alternative explicitly.

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?

Usage is only implied: the paging parameters signal this is for enumerating the full set of pages. There is no explicit guidance on when to use this versus allbirds_page (single page by handle) or the sitemap siblings, and no prerequisites are stated.

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