Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bbb_article

Fetch published BBB article metadata, authors, body text, and links from a canonical bbb.org URL. Handles merged or invalid URLs with clear errors.

Instructions

Get a BBB article. Returns published BBB article metadata, author names, body text, and useful links from a canonical public article URL on www.bbb.org or bbb.org. If BBB merges a story into another BBB article, the response contains the target article's id and source_url plus the original requested_url. Returns a permanent 404 when BBB moves the URL to an evergreen /all/ page or outside bbb.org, when BBB redirects the URL back to itself so it cannot be loaded, or when the URL resolves to a published non-article type such as an event; safe HTTPS destinations are named in the error and are never fetched.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical BBB article URL on www.bbb.org or bbb.org

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.13
    • changedInput schema / properties / url / description
      Previous value: -"Canonical BBB article URL"New value: +"Canonical BBB article URL on www.bbb.org or bbb.org"
  2. Addedv1.17.12

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations to lean on, the description carries the full burden and does so richly: it enumerates return content (metadata, author names, body text, links), discloses merge/redirect behavior with the target id and source_url plus requested_url, and specifies the exact 404 conditions. It even notes that safe HTTPS destinations are named in the error and never fetched, a meaningful safety disclosure.

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 'Get a BBB article' followed by the most decision-relevant facts (return content, URL requirement). The dense 404 sentence is long but every clause conveys a distinct edge case an agent needs, so it earns its place despite the density.

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?

For a one-param tool with no output schema and no annotations, the description covers response content, redirect/merge handling, and error behavior thoroughly. The only minor gap is that 'metadata' is left generic and no field-level return detail is given, but it is adequate without an output schema.

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?

The single url parameter has 100% schema coverage, so baseline is 3; the description adds meaning by specifying the URL must be a 'canonical public article URL' on bbb.org or www.bbb.org, and by explaining the behaviors triggered by various URL resolutions (merges, evergreen /all/ pages, non-article types).

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?

Names a specific verb+resource ('Get a BBB article') and immediately scopes the input to a canonical public article URL on www.bbb.org or bbb.org. This clearly distinguishes it from sibling page/news tools like bbb_news, bbb_page, and bbb_search.

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?

The description implies usage by requiring a 'canonical public article URL' and details when the tool will not work (404 cases), which is useful context. However, it never explicitly routes the agent to an alternative tool (e.g., how to obtain a canonical article URL, or when to prefer bbb_news/bbb_search), so the when-to-use guidance remains 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