Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

bbb_news_topics

List BBB newsroom topics. Returns the complete topic navigation shown by a BBB newsroom page, including its active topic.

Instructions

List BBB newsroom topics. Returns the complete topic navigation shown by a BBB newsroom page, including its active topic. The page can be the US or Canada newsroom, a state, province or city newsroom, or one local BBB chapter's newsroom; the returned topic URLs stay in that scope, and a chapter has its own topic set.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical https://www.bbb.org newsroom URL, optionally with a topic segment: /us/news or /ca/news; /<country>/<state>/news or /<country>/<state>/<city>/news with country us or ca, the two-letter region code from bbb-regions and the city slug from a business profile URL; or a chapter's news_url from bbb-local-bbbs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose real behavior: returned topic URLs stay within the given scope, and a chapter has its own topic set. However it never explicitly states this is a safe read-only operation, nor covers pagination, response shape, or auth needs.

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?

Three sentences, front-loaded with the core purpose, then scoping and chapter behavior. No filler, though the final clause about chapter topic sets is slightly tangential.

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 single-parameter, read-only list tool with no output schema, the description covers purpose, accepted input scopes, and return content adequately. It could be more explicit about read-only semantics but is otherwise complete.

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 url format is fully documented in the schema; baseline is 3. The description reinforces the accepted scopes (country/state/city/chapter newsrooms) but adds little syntax or format detail beyond the schema.

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+resource ('List BBB newsroom topics') and clarifies what is returned ('the complete topic navigation... including its active topic'). It is clearly a topic/navigation tool distinct from bbb_news (articles), though it never names a sibling to draw that contrast explicitly.

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: it tells the agent which newsroom URLs are valid (US/Canada/state/province/city/chapter), which is helpful context, but gives no explicit when-to-use, when-not, or alternative (e.g., bbb_news for articles). The agent must infer the selection criteria.

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