Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brave_news

Search news articles via Brave by query, with country, language, date range, and pagination controls. Returns structured JSON results or 503 when results are unavailable.

Instructions

Search Brave news results. Returns Brave news search results for a query string. Locale defaults to country=us and lang=en-us. Returns 503 when Brave serves a challenge page or unusable results.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
langNoBrave UI language; defaults to en-us
countNoResults to return; defaults to 10, clamped to 1..50
offsetNoZero-based Brave result page; defaults to 0
countryNoBrave result country; defaults to us
date_toNoCustom end date in YYYY-MM-DD; requires date_from
date_fromNoCustom start date in YYYY-MM-DD; requires date_to
time_rangeNoPreset time filter: any, day, week, month, year, or custom

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "all",
+  "ar",
+  "at",
+  "au",
+  "be",
+  "br",
+  "ca",
+  "ch",
+  "cl",
+  "cn",
+  "de",
+  "dk",
+  "es",
+  "fi",
+  "fr",
+  "gb",
+  "gr",
+  "hk",
+  "id",
+  "in",
+  "it",
+  "jp",
+  "kr",
+  "mx",
+  "my",
+  "nl",
+  "no",
+  "nz",
+  "ph",
+  "pl",
+  "pt",
+  "ru",
+  "sa",
+  "se",
+  "sg",
+  "tr",
+  "tw",
+  "us",
+  "za"
+]
    • addedInput schema / properties / lang / enum
      Added value: +[
+  "de-de",
+  "en-ca",
+  "en-gb",
+  "en-in",
+  "en-us",
+  "fi-fi",
+  "fr-ca",
+  "fr-fr",
+  "ja-jp",
+  "pt-br",
+  "sq-al",
+  "sw-ke",
+  "zh-tw"
+]
    • addedInput schema / properties / time_range / enum
      Added value: +[
+  "any",
+  "day",
+  "week",
+  "month",
+  "year",
+  "custom"
+]
  2. Addedv1.6.0
  3. Removedv1.6.0
  4. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose a genuinely non-obvious behavior (503 on challenge pages/unusable results), which is valuable. But the locale-default sentence merely restates the schema defaults, and it says nothing about rate limits, auth, or result shape beyond 'news search results'.

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 short sentences, front-loaded with the purpose before the defaults and the error caveat. Little waste, though the locale-default sentence is largely redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search tool with no output schema and no annotations, the description is only marginally adequate. It covers the error case but says nothing about what a result contains, ordering, or how the three time-filter parameters interact.

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%: every parameter, including the date_from/date_to mutual dependency and the count clamp, is documented in the schema. The description adds nothing about parameter usage, so the baseline of 3 is appropriate.

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 (Search) and resource (Brave news results), and the repeated 'news' framing distinguishes it from the sibling web/images/videos search tools by resource type. However, it never names brave_search or brave_images explicitly, so an agent must infer the split from the tool name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance is given. With four near-identical siblings (brave_search, brave_images, brave_videos, brave_suggest), the description never states when news search is preferable to general web search, nor any exclusions. Usage is only implied by the word 'news'.

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