Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

balenciaga_product_variants

Fetch live Balenciaga product color and size variations by URL, including variation IDs, sellability flags, availability, care text, and related product IDs.

Instructions

Get Balenciaga product variations. Returns Balenciaga's live color/size variation matrix for a product, including variation ids, selection/sellability flags, care text, availability, and related product ids. url may be a product URL or a Product-Variation URL from balenciaga-product's colors[].url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesBalenciaga product URL or Product-Variation URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are present, so the description carries the disclosure burden. It reveals the 'live' nature of the matrix and lists the data fields returned, but doesn't mention auth, rate limits, error behavior, or response structure. Adequate but not rich.

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?

Two sentences with no filler. The purpose is front-loaded, and the second sentence efficiently packs return contents and parameter guidance.

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 single-parameter get tool with no output schema, the description covers input variants and return contents well. It lacks explicit sibling differentiation and caveats about availability or errors, but nothing critical is missing for correct invocation.

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 baseline is 3. The description adds meaningful context beyond the schema by specifying that the Product-Variation URL comes from balenciaga-product's colors[].url, which helps the agent construct or recognize valid inputs.

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?

Description states a specific verb ('Get') and resource ('Balenciaga product variations'), and enumerates the returned data: variation ids, selection/sellability flags, care text, availability, related product ids. This clearly differentiates it from balenciaga_product and other Balenciaga tools.

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?

The description explains that url may be a product URL or a Product-Variation URL sourced from balenciaga-product's colors[].url, giving concrete input guidance. It doesn't explicitly state when to prefer this tool over balenciaga_product, but the reference to balenciaga-product's colors[].url implies the relationship.

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