Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

farfetch_search

Search Farfetch listings by department plus designer or category filter, returning name, brand, price, image, availability, and page count.

Instructions

Search Farfetch listings. Browses Farfetch's luxury multi-brand marketplace by department plus a designer and/or category filter (at least one is required), returning listing summaries (name, brand, price, image, availability) and the upstream page count.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1
genderYesDepartment: women, men, kids
categoryNoCategory slug from GET /farfetch/categories; designer or category is required
designerNoDesigner slug from GET /farfetch/designers; designer or category is required

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return shape (name, brand, price, image, availability plus upstream page count) and the filter precondition. It does not cover auth, rate limits, or pagination limits, but for a read-only search the disclosure is solid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, zero waste, with the operation and filter precondition front-loaded and the return contents trailing. Every clause earns its place.

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, and the description compensates by enumerating the returned listing fields and the page count. Combined with the required-filter rule, an agent has everything needed to call it correctly.

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% and the schema already documents gender, designer/category slugs, and the required-filter rule, so the description largely repeats structured data. It adds only the framing of department vs designer/category, which is baseline-level value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search/browse) and resource (Farfetch luxury marketplace listings), and specifies how the filters combine (department plus designer and/or category). An agent can distinguish this from farfetch_product (detail) and farfetch_categories/designers (slug sources) without opening a schema.

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 a concrete usage constraint — at least one of designer or category is required alongside department — which steers correct invocation. It stops short of explicitly naming alternatives (e.g. 'use farfetch_product for full details'), so it is clear context but without full routing guidance.

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