Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fresha_landing_venues

Lists venues published on a Fresha landing page by city, business type, or treatment type, returning names, addresses, ratings, price bands, and images.

Instructions

List the venues on one Fresha landing page. Returns the venue list Fresha (fresha.com) publishes on one of its own pre-rendered landing pages: each venue's name, canonical page, published business types, postal address with coordinates, average rating with its rating count, the venue's coarse price band and an image. Read a plain city page with city alone, a business-type page with business_type, or a treatment-type page with treatment_type; the two facets are mutually exclusive. city is the page's own value with its country prefix, e.g. us-new-york. There is no pagination on this route: Fresha pre-renders a fixed list (about 30 venues on a city page, 130 on a business-type or treatment-type page) and exposes no page parameter, so count is the number of venues on the page and never a total. A facet combination Fresha does not publish is a not-found. The price range is the venue's own coarse display string and is not this API's price surface: a venue's service menu, read through fresha-venue, is.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "fresha_landing_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity landing value with country prefix, e.g. us-new-york
business_typeNoBusiness-type slug, e.g. hair-salons; mutually exclusive with treatment_type
treatment_typeNoTreatment-type slug, e.g. hair-colouring; mutually exclusive with business_type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses non-obvious behavior: there is no pagination, Fresha pre-renders a fixed list (about 30 on city pages, 130 on facet pages), count is page size rather than a total, and unpublished facet combinations return not-found. These are exactly the operational details an agent needs.

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?

The purpose is front-loaded and most sentences earn their place by covering pagination, counts, not-found cases, and the price-surface distinction. However, the final sentence is an awkward fragment and the paragraph is dense enough that a small amount of structure would improve readability.

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?

Although there is no output schema, the description enumerates the returned venue fields (name, canonical page, business types, address with coordinates, rating and count, price band, image). It also covers pagination, facet behavior, not-found behavior, and the related fresha-venue alternative for pricing detail.

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%, so the baseline is 3, but the description adds useful meaning beyond the schema by mapping city to a page's own country-prefixed value and explaining which parameter selects which page type. The mutual-exclusivity note is also reinforced in context.

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?

The description uses a specific verb and resource: it lists venues from one Fresha landing page. It also distinguishes the page types (city, business-type, treatment-type) and implies the difference from fresha_search_venues and fresha_venue by describing pre-rendered landing-page content rather than search or a single venue.

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

Usage Guidelines5/5

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

It explicitly says to use city alone for a plain city page, business_type for a business-type page, or treatment_type for a treatment-type page, and states that the two facets are mutually exclusive. It also routes price/menu lookups to fresha-venue, giving a clear alternative.

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