Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

allbirds_search_suggest

Retrieve Allbirds search suggestions for products, collections, and queries to enhance storefront search.

Instructions

Get Allbirds search suggestions. Returns products, collections, and query suggestions from Allbirds's (https://www.allbirds.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/5.0
Behavior3/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. It usefully discloses the return categories and that the storefront URL is fixed server-side (so no URL parameter is needed), and "Get" implies a safe read. However it says nothing about permissions, rate limits, or whether the call is purely non-mutating beyond the verb choice.

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 purpose, followed by return contents and one scoping constraint. No filler, no restating of the name.

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 three-parameter read tool with no output schema, the description covers purpose, return categories, and the fixed-URL constraint, which is enough to call it correctly. Only the absence of any routing guidance relative to sibling tools keeps it from being fully complete.

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 q, limit, and types are already documented in the schema; the description's mention of the three suggestion categories loosely mirrors the `types` values but adds no syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description names a specific verb and resource ("Get Allbirds search suggestions") and scopes it to the Allbirds brand, which is exactly what separates it from the many other *_search_suggest siblings. It further specifies what the suggestions contain (products, collections, query suggestions), so an agent can distinguish it from allbirds_products or allbirds_collections without opening the schema.

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?

Calling it "predictive search" implies the autocomplete/typeahead use case, but the description never states when to prefer this over the sibling allbirds_products, allbirds_collections, or allbirds_search tools, nor any prerequisites. Usage is implied rather than directed.

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