Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbb_business_complaints

Fetch a BBB business's complaint history: total complaints, 12-month closed/filed counts, and per-complaint details with pagination.

Instructions

Get a Better Business Bureau business's complaint history. Returns a business's BBB complaint history: total complaint count, complaints closed or filed in the last 12 months, and one page of per-complaint detail (date, type, status, narrative text, and any business response / customer answer thread). Complaints are listed newest first, 10 per page; use page with the returned page, total_pages and has_more to walk the full list. A business with no filed complaints returns total_complaints 0 and an empty complaints list -- this is a normal result, not an error.

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
pageNoComplaint list page, 1 or greater (10 complaints per page, newest first). Defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.12
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Complaint list page, 1 or greater (10 complaints per page, newest first). Defaults to 1",
+  "type": "integer"
+}
    • 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.2/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 full behavioral burden, and it does well: it discloses the return shape, newest-first ordering, 10-per-page size, and explicitly clarifies that a zero-complaint business returns total_complaints 0 with an empty list rather than an error. It omits auth/rate-limit behavior, but the output semantics are unusually well disclosed.

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-loaded with the purpose, and each sentence conveys actionable detail (return contents, pagination, empty-result semantics). Minor redundancy between the opening "Get...complaint history" and the following "Returns a business's BBB complaint history" keeps it from a 5.

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?

With no output schema and only two parameters, the description fully covers what an agent needs: where the URL comes from, how pagination works, what each complaint record contains, and how to interpret the empty case. Nothing essential is missing.

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 both parameters are already documented and the baseline is 3. The description adds value beyond the schema by explaining how page interacts with returned page/total_pages/has_more to page through results, which the schema does not state.

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 and resource ("Get a Better Business Bureau business's complaint history") and distinguishes itself from the sibling review/info tools by naming complaints specifically. An agent can tell this apart from bbb_business_reviews or bbb_business 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 Guidelines3/5

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

Provides operational context (URL comes from a bbb-search result; use page with returned page/total_pages/has_more to walk the list), which is useful. However, it never states when this tool is preferable to the many sibling BBB tools (reviews, more_info, scamtracker), so the routing guidance is only implied.

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