Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

balenciaga_search

Search Balenciaga's storefront by keyword, sort by price or latest, and filter by exact facets. Get paginated product lists as clean JSON.

Instructions

Search Balenciaga products. Searches Balenciaga's storefront by keyword using the site's own product-grid fragment. q is required; sort accepts latest, price_ascending, or price_descending; page is one-based with 12 products per page; and filters accepts comma-separated exact field:value pairs from live facets. Repeat a field to OR multiple values within that facet. A genuine no-result query returns an empty products list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesFree-text search query
pageNoOne-based page number, defaults to 1
sortNoSort order
filtersNoComma-separated exact facet filters; repeat a field for OR values, for example akeneo_macroColor:BLACK,akeneo_macroColor:WHITE

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses the internal product-grid source, exact facet matching semantics, OR behavior for repeated fields, one-based pagination with 12 items per page, and the empty-list behavior for no results. This is substantial behavioral context.

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?

Four dense sentences with no filler. The purpose is front-loaded, and each subsequent sentence explains a distinct parameter or behavior. The structure is easy to parse and every sentence earns its 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 4-parameter search tool with no output schema, the description covers all input semantics, pagination, sorting, filtering syntax, and a key edge case. It does not detail the product object structure in the response, but the phrase 'products list' gives a reasonable expectation of the return shape.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema: it specifies the page size (12 products per page) and that filters come from live facets with exact field:value pairs. It also restates sort options, which is redundant but harmless.

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 explicitly states 'Search Balenciaga products' and clarifies it uses a keyword-based storefront search. This clearly differentiates it from sibling tools like balenciaga_categories, balenciaga_product, or balenciaga_product_variants, which serve browsing or detail purposes.

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?

Clear context is provided: this is for keyword search on the Balenciaga storefront, with required q and optional sort/page/filters. However, the description never explicitly names alternatives or states when not to use this tool versus balenciaga_category or balenciaga_product.

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