Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bbb_scamtracker_search

Search Better Business Bureau Scam Tracker reports by free-text query, scam category, state, date range, or dollar loss to find consumer-reported scam incidents.

Instructions

Search Better Business Bureau Scam Tracker reports. Searches bbb.org Scam Tracker's consumer-reported-scam database by free-text query, scam category, targeted-victim state/province, reported-scammer state/province, report-date range, and/or dollar-loss range, paginated 10 results/page. A verified search with no matches returns results: [] and total_results: 0; an unavailable or unrecognized page returns 503 rather than an empty list. When result cards are present but BBB's total count is unavailable, total_results is omitted. Every page returns has_more and, when BBB's result count is exact, total_pages: request the next page only while has_more is true, because a page past the end returns 404. Omit every filter to browse the most-recent-first feed. This is a separate BBB dataset from the bbb-search/bbb-business/bbb-business-complaints business-rating family -- consumer-reported scam incidents, not business ratings.

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (10 per page), default 1
queryNoFree-text search (phone number, website, email, business name, scam ID, description). Omit to browse the most-recent feed
stateNoOptional 2-letter targeted-victim state/province code (US state or Canadian province)
date_toNoOptional report-date range end (YYYY-MM-DD), inclusive. Must be set together with date_from
date_fromNoOptional report-date range start (YYYY-MM-DD), inclusive. Must be set together with date_to
scam_typeNoScam category filter
scammer_stateNoOptional 2-letter reported-scammer state/province code (US state or Canadian province) -- where the scammer is reported to be, not the victim
max_dollars_lostNoOptional maximum reported dollar loss. Must be set together with min_dollars_lost
min_dollars_lostNoOptional minimum reported dollar loss. Must be set together with max_dollars_lost

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / scam_type / enum
      Added value: +[
      +  "Advance Fee Loan",
      +  "Bank/Credit Card Company Imposter",
      +  "Business Email Compromise",
      +  "Charity",
      +  "Counterfeit Product",
      +  "COVID-19",
      +  "Credit Cards",
      +  "Credit Repair/Debt Relief",
      +  "CryptoCurrency",
      +  "Debt Collections",
      +  "Employment",
      +  "Fake Check/Money Order",
      +  "Fake Invoice/Supplier Bill",
      +  "Family/Friend Emergency",
      +  "Foreign Money Exchange",
      +  "Government Agency Imposter",
      +  "Government Grant",
      +  "Healthcare/Medicaid/Medicare",
      +  "Home Improvement",
      +  "Identity Theft",
      +  "Investment",
      +  "Moving",
      +  "Online Purchase",
      +  "Other",
      +  "Phishing",
      +  "Rental",
      +  "Retail Business",
      +  "Romance",
      +  "Scholarship",
      +  "Sweepstakes/Lottery/Prizes",
      +  "Tax Collection",
      +  "Tech Support",
      +  "Travel/Vacation/Timeshare",
      +  "Utility",
      +  "Vanity Award",
      +  "Worthless Problem-solving Service",
      +  "Yellow Pages/Directories"
      +]
  2. Addedv1.16.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: 10 results/page pagination, empty-match vs 503-on-unavailable-page distinction, conditional omission of total_results, has_more/total_pages semantics, and 404 on pages past the end. These are exactly the edge behaviors an agent needs to page safely.

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 purpose and scope, then behavior. It is on the longer side with several semicolon-joined behavioral clauses, but nearly every sentence conveys actionable paging/error information rather than filler.

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?

No output schema exists, so the description must explain returns—and it does (results, total_results, has_more, total_pages, 404/503 failure modes). Combined with 100% schema coverage on inputs, an agent has everything needed to call and page this tool correctly.

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 the schema already documents all 9 parameters, including enum values and paired-filter constraints. The description restates the filter set (query, category, victim/scammer state, date range, dollar range) but adds no syntax or format detail beyond the schema, so the baseline of 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 and resource ('Search Better Business Bureau Scam Tracker reports') and explicitly scopes it to BBB's consumer-reported-scam database. It directly distinguishes itself from the sibling business-rating family (bbb-search/bbb-business/bbb-business-complaints), so an agent can route correctly 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 Guidelines5/5

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

Gives explicit routing: 'Omit every filter to browse the most-recent-first feed,' and names the alternative dataset family it is NOT part of. The conditions that select this tool over its BBB siblings are stated rather than 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