Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

booksy_business

Retrieve one Booksy business's public profile by numeric ID, including service menu with prices and durations, hours, address, contact links, and review scores.

Instructions

Get one Booksy business's detail record. Returns one Booksy (booksy.com) business: name, slug, description, the website's own listing path token (<businessId>_<slug>_<categorySlug>_<cityId>_<citySlug>, served by the app and usable to join the two surfaces), every category with its web slug, the geographic chain from country down to zip with numeric ids, address and coordinates, cover and logo images, the complete partner-defined service menu with prices and durations, opening hours, amenities, booking policy text, public contact links and aggregate review scores. This is the Android app's JSON detail route (/core/v2/customer_api/businesses/{id}/), so one business costs a few tens of kilobytes instead of a rendered page. An unknown id is a 404. Review text, reviewer identities, staff identities, client records and any availability, booking or payment data are never returned.

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": {
      "id": "<id>"
    },
    "name": "booksy_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Booksy business id
countryNoMarket host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does so well: it discloses the response surface field-by-field, the 404 behavior for an unknown id, approximate payload size, the upstream route, and an explicit negative contract (no review text, reviewer or staff identities, client records, availability, booking, or payment data). That negative contract is exactly the kind of behavioral boundary annotations would otherwise provide.

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?

Purpose is front-loaded in the first clause, and the long returned-field enumeration is dense but each item is concrete rather than filler. The single middle sentence sprawls across roughly ten comma-separated payload elements, which makes it harder to scan than a short bulleted or grouped layout would be.

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?

There is no output schema, so the description must define the return shape, and it does so comprehensively down to nested details like the geographic chain and per-category web slugs. Error behavior (404), payload size, and the deliberate absence of personal, availability, and payment data round out what an agent needs before calling.

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 both parameters are already documented, and the enum for country is defined in the schema as the "market host." The description adds only a modest cross-reference by showing that the id is the `businessId` component of the `<businessId>_<slug>_<categorySlug>_<cityId>_<citySlug>` listing token; that is a useful join hint but not a semantic explanation of how country changes the result.

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?

Opens with a specific verb and resource ("Get one Booksy business's detail record") and enumerates the exact payload, so the agent knows precisely what comes back. It never names or contrasts with the obvious sibling booksy_businesses, so the singular-vs-plural distinction must be inferred from the tool name alone.

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: knowing it hits the Android app's JSON detail route and costs "a few tens of kilobytes instead of a rendered page" tells the agent it is a detail lookup, not a search. There is no explicit guidance on when to choose this over booksy_businesses, no prerequisites, and no stated exclusions beyond the field-level negatives.

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