Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbb_business_reviews

Fetch Better Business Bureau customer reviews for a business profile, including ratings, dates, text, replies, average score, and total count, with 10 results per page.

Instructions

Get a Better Business Bureau business's customer reviews. Returns a business's full customer-review list (author, star rating, date, text, and any business response thread), paginated 10 per page, plus the average star rating and total review count.

Input Schema

NameRequiredDescriptionDefault
urlYesBBB business profile URL, from a bbb-search result's url or hq_profile_url. A location URL ending in /addressId/<number> is accepted and read from the business profile
pageNoResult page (10 per page), default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / url / description
      Previous value: -"BBB business profile URL, from a bbb-search result's url or hq_profile_url"New value: +"BBB business profile URL, from a bbb-search result's url or hq_profile_url. A location URL ending in /addressId/<number> is accepted and read from the business profile"
  2. Addedv1.16.0

TDQS

A4/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 the burden and largely does so: it discloses the pagination size (10 per page) and the composition of each review (author, star rating, date, text, response thread) plus aggregate average rating and total count. It omits auth requirements, rate limits, or behavior on invalid URLs, but adds meaningful behavioral context.

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 front-loaded sentences with no filler; the primary function is stated first, then the return shape. Every clause earns its place.

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 correctly fills the gap by enumerating the returned fields and aggregates. Combined with the fully documented input schema, an agent has enough to call the tool correctly, though the absence of any error/auth notes leaves a minor gap.

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%, so both parameters are already documented (url format, page default). The description's 'paginated 10 per page' merely restates the schema and adds no parameter semantics beyond it, so the baseline 3 applies.

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 (Get) and resource (a BBB business's customer reviews), and distinguishes itself from siblings like bbb_business_complaints by scoping to reviews. An agent can tell the tool's function without opening the schema.

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 implied — call it to retrieve reviews for a business — but there is no explicit when-to-use or when-not-to-use guidance, and no mention of related siblings (e.g., bbb_business_complaints or bbb_business) that an agent might confuse it with.

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