Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_collections

List Fashionphile storefront collections with pagination controls. Set page and limit to fetch up to 250 records per request via Crawlora MCP.

Instructions

List Fashionphile collections. Returns collections from Fashionphile (https://www.fashionphile.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does add meaningful behavioral context: the storefront URL is fixed server-side, and valid empty pages return 200 with an empty collections array. This usefully tells the agent not to treat an empty array as an error. It doesn't cover mutability or permissions, but for a listing endpoint that is expected.

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. Minor redundancy in restating 'from Fashionphile (https://...)' after already naming the resource, but nothing wasteful enough to hurt.

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?

With no output schema, the description covers the key edge case (empty result pages) and the server-side URL fix, which is enough for a two-optional-param listing tool whose parameters are fully schema-documented. The main missing piece is routing guidance vs. sibling tools.

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 coverage is 100%, so both page and limit are fully documented in the schema. The description adds nothing about pagination syntax or limits beyond what the schema provides, so 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+resource: 'List Fashionphile collections.' An agent can distinguish this as a collection-listing tool. It doesn't explicitly differentiate from siblings like fashionphile_collection_products, but the scope is clear.

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 indication of when to use this vs. related siblings such as fashionphile_collection_products or fashionphile_search. No prerequisites or exclusion conditions are given, so the agent must infer usage from the name alone.

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