Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

balenciaga_category

Retrieve Balenciaga category listings by path, with page, sort, and facet filters to get specific product results.

Instructions

Browse a Balenciaga category. Returns one Balenciaga category listing from the site's own Search-ShowAjax fragment. path comes from balenciaga-categories. sort accepts latest, price_ascending, or price_descending. filters is a comma-separated list of exact field:value pairs from the response's live facets; repeat a field to OR multiple values within that facet; omit it for an unfiltered listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page number, defaults to 1
pathYesCategory path from balenciaga-categories
sortNoSort order
limitNoProducts per page, defaults to 16, maximum 48
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

A3.6/5.0
Behavior3/5

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

No annotations provided; description includes technical detail about Search-ShowAjax fragment and live facets but omits read-only status, auth requirements, pagination behavior, or error semantics.

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 sentences, front-loaded with purpose, then parameter usage; every sentence earns its place with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations; description gives basic purpose but not what the listing contains, error behavior, or interaction between page/limit and filters. Sufficient for a simple call but not fully self-contained.

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 100%, baseline 3, but description adds meaning: path provenance, valid sort values, and especially detailed filters semantics (exact field:value pairs, OR repetition, omission for unfiltered) which go beyond the schema.

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 it browses a Balenciaga category and returns one category listing, and points to path source. Clear verb+resource but doesn't explicitly contrast with sibling balenciaga_search or balenciaga_categories.

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?

Implied usage: use it when you have a path from balenciaga-categories and want a category listing. No when-not-to-use guidance or comparison to alternatives like balenciaga_search.

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