Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_search

Search Fashionphile products via full-text and faceted filters; returns ranked listings with condition grades and discounts.

Instructions

Search Fashionphile products. Returns ranked products from Fashionphile's (https://www.fashionphile.com) own full-text and faceted product search, including condition grade, discount percentage, and other filter attributes not available from the classic catalog endpoints in this family. The storefront URL is fixed server-side. Omitting q browses the full catalog subject to any condition/vendor/availability filters and the chosen sort. By default only in-stock listings are searched, matching the storefront; availability=sold searches the sold archive instead. total_items is the exact number of products matching the query and all filters.

Input Schema

NameRequiredDescriptionDefault
qNoSearch query text
pageNo1-based page, defaults to 1
sortNoSort order. Allowed values: relevance, newest, price_asc, price_desc
limitNoMaximum products, defaults to 20 and supports up to 50
vendorNoFilter by exact designer/vendor name, e.g. Chanel
conditionNoFilter by condition grade. Allowed values: New, Excellent, Giftable, Shows Wear, Worn, Flawed, Fair
availabilityNoWhich listings to search. Allowed values: available (in-stock only, default), sold (sold archive only), all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 that results are ranked from the storefront's own faceted search, that the storefront URL is fixed server-side, that only in-stock listings are searched by default, and that `total_items` is exact. It omits auth/rate-limit and pagination behavior, but the behavioral profile is otherwise solid.

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-loads the purpose in the first sentence, then layers scope and default-behavior details. Mostly dense and earning its sentences, though it is a long paragraph where a bulleted structure would be slightly easier to parse.

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?

For a 7-param search tool with no annotations and no output schema, the description covers return content, default filtering, availability modes, and result-count semantics. It is nearly complete, lacking only explicit pagination/limit flow and auth/prereq notes.

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 coverage is 100% (baseline 3), and the description adds meaning beyond the schema: omitting `q` browses the catalog, the default `availability` is in-stock matching the storefront, and `availability=sold` switches to the archive. This enriches the availability and query semantics usefully.

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 clear verb+resource ('Search Fashionphile products') and distinguishes itself from siblings by noting it returns condition grade, discount percentage, and filter attributes 'not available from the classic catalog endpoints in this family.' An agent can tell it apart from fashionphile_products, though no sibling is named explicitly.

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?

Gives useful usage context: omitting `q` browses the full catalog, the default searches only in-stock listings, and `availability=sold` targets the sold archive. It stops short of explicitly routing the agent ('use X when Y'), so it is clear context without exclusions.

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