Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionnova_products

Retrieve Fashion Nova product listings from its public catalog, using page and limit parameters to browse inventory.

Instructions

List Fashion Nova products. Returns products from Fashion Nova's (https://www.fashionnova.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty products array.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum products, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load and it does disclose two useful facts: the storefront URL is fixed server-side (no URL parameter needed) and empty pages return 200 with an empty array (pagination termination signal). It omits auth requirements, rate limits, and result ordering, so it is 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.

Conciseness4/5

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

Three short sentences, front-loaded with the core purpose ('List Fashion Nova products'), followed by scope and pagination behavior. No filler, though the URL parenthetical is slightly expendable.

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 two-param paginated listing tool with full schema coverage and no output schema, the description is nearly sufficient, but it leaves the agent without sibling routing guidance in a toolset crowded with fashionnova_* variants.

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%, so both parameters (page 1-based default 1, limit default 50 max 250) are fully documented in the schema. The description only implies pagination via the 'empty result pages' note and adds no syntactic detail beyond the schema, so 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?

States a specific verb (List) and resource (Fashion Nova products) with the scope clarified as the public catalog. However, it does not differentiate from close siblings like fashionnova_collection_products, fashionnova_product, or fashionnova_page, which an agent must disambiguate on its own.

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 guidance on when to use this catalog-listing tool versus siblings such as fashionnova_collection_products (collection-scoped listing) or fashionnova_product (single-item detail). No prerequisites or exclusions are stated.

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