Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brave_search

Search the web with Brave Search to return results, related queries, discussions, videos, and knowledge cards. Filter by date range, country, or language for targeted research.

Instructions

Search Brave. Returns web search results from Brave Search for a query string, along with offset-based pagination, related queries, discussions, videos, and the right-side knowledge card when Brave includes one. Use time_range for preset ranges or date_from/date_to for a custom YYYY-MM-DD range. Locale defaults to country=us and lang=en-us.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
langNoBrave UI language; defaults to en-us
offsetNoZero-based Brave result page
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

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 behavioral burden. It does disclose the return shape well (offset-based pagination, related queries, discussions, videos, optional knowledge card), which is useful. However it says nothing about rate limits, authentication, or result caps for a network-facing search tool.

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 purpose then output then parameter hints; very little waste. The return-content enumeration is slightly padded but each clause is informative.

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?

There is no output schema, so the description steps in to describe the returned content and pagination, which it does adequately. With no annotations it could say more about safety/auth, but for a read-only search tool nothing critical is missing to call it 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 seven parameters, giving a baseline of 3. The description adds modest value by clarifying the time_range vs date_from/date_to relationship and the locale default, but adds nothing the schema doesn't already imply.

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 and resource ("Search Brave", "Returns web search results from Brave Search for a query string") and enumerates the payload (related queries, discussions, videos, knowledge card). The Brave engine identity partly differentiates it from the many sibling search tools, but it doesn't articulate why to pick it over web_search, bing_search, or duckduckgo_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?

Usage is only implied by the nature of a web search. The one genuine directive ("Use time_range for preset ranges or date_from/date_to for a custom YYYY-MM-DD range") is about parameter selection, not about when this tool is the right choice versus the numerous alternative search tools. No when-not guidance.

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