Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbb_business

Fetch a Better Business Bureau business profile from a bbb.org URL to retrieve BBB rating, accreditation status, years in business, contact details, categories, and a latest-reviews preview.

Instructions

Get a Better Business Bureau business profile. Returns a bbb.org business profile: BBB rating letter grade and reasons, accreditation status and since-date, years in business, BBB file/incorporation dates, entity type, contact info, business categories, social media, and a short latest-reviews preview.

Input Schema

NameRequiredDescriptionDefault
urlYesBBB business profile URL, from a bbb-search result's url or hq_profile_url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the returned profile fields (rating, accreditation, dates, categories, reviews preview), which is useful behavioral context, but it never states that this is a read-only fetch, nor any auth/rate-limit or failure behavior for a tool whose safety profile is undocumented.

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 verb+resource, followed by a single enumeration of returns. The enumeration is long but each field is meaningful for a profile tool with no output schema, so the length is justified even if dense.

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 well by listing the returned fields, which is what an agent needs to decide this is the profile endpoint. It is somewhat thin on where the input URL originates and on mutation/safety context, but the core completeness for calling the tool is present.

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?

The single 'url' parameter is fully documented in the schema (100% coverage), so the description need not repeat it, and it adds no extra syntax or format detail beyond the schema. Baseline 3 applies when the schema already does the heavy lifting.

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?

States a specific verb ('Get') and resource ('Better Business Bureau business profile') and enumerates what the profile contains, so the agent can tell it is the profile-detail endpoint. It does not explicitly name the sibling detail tools (bbb_business_complaints, bbb_business_reviews, bbb_business_more_info) it must be distinguished from, so sibling differentiation is left to inference.

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 by the resource name and the schema note that the URL comes from a bbb-search result. There is no explicit 'when to use this vs bbb_business_reviews/complaints' guidance, and no prerequisites are stated, leaving the agent to infer routing from the name.

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