Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionnova_product_recommendations

Fetch recommended products for a Fashion Nova product handle, with options to set related or complementary intent and a result limit.

Instructions

List Fashion Nova product recommendations. Returns recommended products for one Fashion Nova (https://www.fashionnova.com) product handle. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 10 and supports up to 20
handleYesProduct handle
intentNoRecommendation intent. Allowed values: related, complementary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / intent / enum
      Added value: +[
+  "related",
+  "complementary"
+]
  2. Addedv1.16.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and only notes that 'the storefront URL is fixed server-side' — useful, but it says nothing about whether this is a read-only operation, response size relative to limit, pagination, or what a result item contains. For a tool with zero annotation coverage this is thin.

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?

Three short sentences, front-loaded with the action and resource, and no filler. The trailing note about the fixed storefront URL earns its place but could have been folded into the first sentence without loss.

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?

For a simple read/list tool with fully documented parameters this is minimally adequate, but with no output schema and no annotations the description never characterizes the returned products (fields, ordering, or how many arrive at the default limit). An agent knows what to call but not what to expect back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: limit (max 20, default 10), handle, and the intent enum are all fully documented in the schema. The prose adds nothing beyond the schema about parameter semantics, so the baseline 3 applies.

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?

The description states a specific verb and resource: 'List Fashion Nova product recommendations' returned 'for one ... product handle'. That is enough to distinguish it from the single-product sibling fashionnova_product, though it never explicitly names or contrasts siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or when-not guidance is given. It doesn't say whether this should be called for a known handle only, how it differs from fashionnova_product or fashionnova_products, or when the 'related' vs 'complementary' intent should be chosen. Usage is left entirely to inference.

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