Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

prada_category

Browse a Prada category by ID to retrieve every product and color variant. Filter by gender and sort by price or newest for targeted results.

Instructions

Browse a Prada category. Browses one Prada category by ID, returning every product/color variant in it. category_id is required and must be one of prada-categories' own categories[].id values. gender optionally narrows to one of prada-categories' own genders[].value values. sort selects Prada's own relevance ranking or one of its price/newest orderings. A category with no products returns a well-formed empty result rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page number, defaults to 1
sortNoSort order. Allowed values: suggested, price_asc, price_desc, newest. Defaults to suggested (Prada's own relevance ranking)
limitNoResults per page, defaults to 24, maximum 100
genderNoGender filter. Allowed values: Woman, Man
category_idYesCategory ID, from prada-categories' own categories[].id 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?

Discloses that it returns every product/color variant and returns a well-formed empty result rather than an error for empty categories. Does not mention pagination or error cases for invalid IDs, but schema covers pagination. With no annotations, this description carries the burden well.

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 wasted words. Front-loads the core action and then adds necessary details about required inputs and behavior.

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?

Covers the essential behavior including empty result handling. References the source of valid IDs. Does not detail return structure or pagination, but schema covers parameters. No output schema, so a bit more could be said, but the key behaviors are covered.

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 covers all parameters with descriptions, so baseline 3. Description adds meaning by specifying that category_id and gender must come from prada-categories' own fields, and that sort uses Prada's relevance ranking. This goes beyond the schema's enum descriptions.

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 ('Browses') and resource ('one Prada category by ID'), and specifies output ('every product/color variant'). Distinguishes from siblings like prada_search and prada_product by focusing on category browsing.

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 clear usage context: requires category_id from prada-categories, and optional gender and sort filters. Does not explicitly name alternative tools, but implies the need for category_id first. The context is clear enough for an agent to decide when to use it.

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