Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

bbb_category

Browse BBB businesses by category and location without a free-text query, returning paginated results you can filter by rating, distance, accreditation, and quote availability.

Instructions

Browse a Better Business Bureau category. Browses bbb.org businesses by category and location directly, without a free-text search query. Returns the same business-result shape as bbb-search. A verified empty first page returns results: [] and total_results: 0; an unavailable or unrecognized page returns an error. A page beyond the exact last page returns 404, and a page beyond BBB's 15-page accessible limit returns 404 naming that limit. Optional sort and filter parameters use the same values as bbb-search; query-scoped category and state/province values come from bbb-search-filters.

Input Schema

Name	Required	Description
`url`	Yes	BBB category browse URL, from a bbb-search result's related_categories
`page`	No	Result page, default 1
`sort`	No	Sort order
`state`	No	Query-scoped state or province code from bbb-search-filters
`rating`	No	One or more BBB rating buckets
`distance`	No	Maximum distance in miles; omit for all distances
`get_quote`	No	Only businesses offering quote requests
`accredited`	No	Only BBB-accredited businesses
`category_id`	No	Query-scoped category ID from bbb-search-filters
`service_area`	No	Only businesses serving the searched area

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.17.12Oct 13, 2026

addedInput schema / properties / accredited

Added value: +{
+  "description": "Only BBB-accredited businesses",
+  "type": "boolean"
+}

addedInput schema / properties / category_id

Added value: +{
+  "description": "Query-scoped category ID from bbb-search-filters",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / distance

Added value: +{
+  "description": "Maximum distance in miles; omit for all distances",
+  "enum": [
+    "5",
+    "10",
+    "25",
+    "50",
+    "100"
+  ],
+  "type": "string"
+}

addedInput schema / properties / get_quote

Added value: +{
+  "description": "Only businesses offering quote requests",
+  "type": "boolean"
+}

addedInput schema / properties / rating

Added value: +{
+  "description": "One or more BBB rating buckets",
+  "items": {
+    "enum": [
+      "A",
+      "B",
+      "C",
+      "D",
+      "F"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / service_area

Added value: +{
+  "description": "Only businesses serving the searched area",
+  "type": "boolean"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Sort order",
+  "enum": [
+    "Relevance",
+    "Distance",
+    "Rating",
+    "AToZ",
+    "ZToA"
+  ],
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "Query-scoped state or province code from bbb-search-filters",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Addedv1.16.0Aug 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries full disclosure burden, and it does this well: it specifies the empty-result shape (results: [] and total_results: 0), error behavior for unavailable pages, 404 semantics beyond the last page, and the 15-page accessible limit. It omits auth/permission and rate-limit context, keeping it short of a 5.

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 purpose in the first two sentences and then layers return/error behavior; nearly every sentence carries unique information. It is somewhat dense and could group the error cases more tightly, but there is no filler.

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 and no annotations, the description compensates by referencing the bbb-search result shape and enumerating error/limit cases. It is close to complete for a 10-param browse tool, though it could say more about what the returned business object contains.

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 baseline is 3, but the description adds cross-tool meaning beyond the schema: optional sort/filter values mirror bbb_search and query-scoped category/state values come from bbb-search-filters. That tells the agent where valid enum values originate, which the schema alone does not.

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 (Browse) and resource (BBB category) and immediately distinguishes itself from siblings by noting it works 'without a free-text search query,' implicitly contrasting with bbb_search. An agent can identify the tool's role without opening any 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?

The 'without a free-text search query' clause signals the selecting condition versus bbb_search, and it points to bbb-search-filters for query-scoped category/state values. However, it never states an explicit 'use bbb_search instead when you have a text query' rule, leaving the 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

bbb_category

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools