Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

prada_product

Fetch detailed Prada product data for one product/color variant by pv ID, including price, stock, sizes, alternate colors, and images.

Instructions

Get a Prada product. Returns product-detail data for one Prada product/color variant: name, price, stock, available sizes, breadcrumb, alternate colors, and images. pv is the product/color identifier, returned by prada-search's, prada-category's, and this endpoint's own products[].pv/other_colors[] fields (also the trailing path segment of a Prada product URL). description and the full image gallery are populated on a best-effort basis and may be briefly absent even for a valid pv; every other field is always populated. An unknown pv returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
pvYesProduct/color identifier, from a search, category, or product result's own pv field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that description and the full image gallery are best-effort and may be briefly absent, that every other field is always populated, and that an unknown pv yields a not-found error. It doesn't cover auth or rate limits, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and return fields, then moves to parameter sourcing and caveats. Every sentence carries information, though the return-field enumeration is dense. Appropriately sized overall.

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

Completeness5/5

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

No output schema exists, so the description must describe returns and does so thoroughly (field list), plus error behavior and best-effort caveats. Against a 1-param read tool with no annotations, this covers everything an agent needs to call it correctly.

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 pv field is already documented, giving a baseline of 3. The description adds real value beyond the schema by identifying pv as a product/color identifier and listing every source that produces it, plus the URL-path-segment hint. That is meaningful semantics beyond the structured field.

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?

States a specific verb+resource ('Get a Prada product') and enumerates exactly what is returned (name, price, stock, available sizes, breadcrumb, alternate colors, images). It also distinguishes itself from sibling tools by explaining that pv originates from prada-search, prada-category, and this endpoint's own fields. An agent can identify it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent where pv comes from (prada-search, prada-category, other_colors, or the trailing segment of a product URL), which effectively guides when this tool is the right call. It stops short of explicitly naming a sibling as the alternative when the agent lacks a pv, so it is strong context rather than a full when/when-not routing rule.

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