Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_search_suggest

Retrieve Fashionphile predictive search suggestions by query, returning matching products, collections, and alternative search terms for autocomplete or discovery.

Instructions

Get Fashionphile search suggestions. Returns products, collections, and query suggestions from Fashionphile's (https://www.fashionphile.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape (three suggestion types) and notes the storefront URL is fixed server-side (so no URL parameter exists), but it omits any read-only/auth framing, rate-limit behavior, or how results are ordered/truncated.

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?

Two tight sentences with the core purpose front-loaded; the server-side URL note is a small but non-wasteful clarification that no endpoint/URL argument is expected. Nothing is padded.

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 compensates by enumerating the three returned suggestion categories, which is enough for an agent to interpret results. Missing only minor operational details (pagination/ordering), so it is near-complete for a low-complexity suggestion endpoint.

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 q, limit, and types are already documented in the schema (limit defaults to 10, max 20; types allowed values product/collection/query). The description adds no parameter-level meaning beyond that, 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?

States a specific verb+resource ('Get Fashionphile search suggestions') and defines the return surface as products, collections, and query suggestions from a 'predictive search'. The 'predictive/suggestions' framing implicitly separates it from sibling fashionphile_search, though no sibling is named directly.

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

Usage Guidelines3/5

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

Usage is only implied: the word 'suggestions' and 'predictive search' point to autocomplete-style typing-ahead use, but there is no explicit when-to-use, when-not-to-use, or reference to the alternative fashionphile_search tool. Adequate but leaves routing 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