Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionnova_pages

List Fashion Nova static pages with page and limit controls; each item returns handle, title, URL, content, and dates.

Instructions

List Fashion Nova static pages. Lists Fashion Nova static pages, 50 per page by default (limit, max 250), with page starting at 1. Each page has its handle, title, URL, plain-text content, and created, updated and published dates. When transport_mode is ssr_embedded, items carry only handle, url and updated_at. An empty result returns an empty pages array.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.6/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 default page size (50), the 250 cap, the 1-based page indexing, the fields returned, the reduced field set under transport_mode=ssr_embedded, and the empty-result behavior. It omits things like rate limits or auth needs, but the behavioral surface is otherwise well covered.

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?

Front-loaded and efficient overall, but the first sentence "List Fashion Nova static pages" is immediately restated as "Lists Fashion Nova static pages," which is redundant filler bleeding into the second sentence.

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 the return value, and it does: it enumerates the item fields, flags the transport_mode-dependent field reduction, and specifies the empty-result shape. For a 2-param list tool this is complete.

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 the schema already documents `page` and `limit` completely. The description's restatement of the 50 default, 250 max, and 1-based page adds no meaning beyond the schema, so the baseline 3 is appropriate.

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 and resource ("List Fashion Nova static pages"), which an agent can distinguish from the singular sibling fashionnova_page, which fetches one page. There is no explicit callout of that sibling, so it lands just short of a 5.

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?

The description never says when to use this tool versus fashionnova_page, fashionnova_collections, or fashionnova_products, nor any exclusions or prerequisites. Usage is only implied by the paginated-list framing.

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