Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

balenciaga_product

Extract structured product details from a Balenciaga product URL, including schema.org name, SKU, price, availability, images, color variants, and product info. Use listing/search result URLs.

Instructions

Get a Balenciaga product. Returns structured product detail from Balenciaga's product page, including schema.org name/SKU/price/availability, images, color variants, and visible product details. url must be a product URL returned by balenciaga-category or balenciaga-search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesProduct URL from a Balenciaga listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 transparency burden. It discloses that the tool reads a product page and returns structured fields, and the 'Get'/'Returns' language implies a read-only operation. It does not mention failure modes, rate limits, or whether the page is scraped live, which would add more 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?

Two sentences with no filler; the core action and return contents are front-loaded, and the URL constraint is placed at the end. Every sentence contributes useful 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?

For a one-parameter fetch tool, the description covers what the tool returns and where valid URLs come from, which is sufficient for correct invocation. It does not describe error behavior or output schema, but those are less critical given the simple input and explicit return summary.

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% for the single url parameter, so the schema already documents the parameter. The description adds value by constraining the URL to product URLs produced by balenciaga-category or balenciaga-search, which is not in 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 a specific action ('Get a Balenciaga product') and enumerates the returned data (schema.org name/SKU/price/availability, images, color variants, visible product details). It clearly identifies the resource, though it does not explicitly contrast itself with balenciaga_product_variants or balenciaga_search, so it stops short of full sibling differentiation.

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?

Provides concrete sourcing guidance: the url must be a product URL returned by balenciaga-category or balenciaga-search. This tells the agent where to obtain valid input, but it does not state exclusions such as when to prefer balenciaga_product_variants.

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