Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brave_images

Search Brave image results for a query string and return structured JSON with pagination, locale, and country controls.

Instructions

Search Brave image results. Returns Brave image 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
+]
  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 are provided, so the description carries the full burden. It does add genuine behavioral value by disclosing the 503-on-challenge-page failure mode, which is non-obvious. It omits auth requirements, rate limits, and any return-format details, leaving significant gaps for a no-annotation 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?

Front-loaded with the core purpose and kept to three short sentences. There is mild redundancy between 'Search Brave image results' and 'Returns Brave image search results for a query string', but the wasted space is minimal.

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?

No output schema exists, so the description should hint at return values; it says it returns image results and documents the 503 failure case, which is adequate. It could say more about result shape or pagination behavior for the count/offset parameters.

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 baseline is 3. The description restates the country=us and lang=en-us defaults, which the schema already documents verbatim, adding no meaning beyond the structured fields for count, offset, or q.

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 image results') and clearly names the image modality, distinguishing it from siblings like brave_search, brave_news, and brave_videos within the same provider family. However, it offers no differentiation against competing image search tools such as bing_images or duckduckgo_image, so it falls short of a 5.

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?

The description gives no when-to-use guidance and no exclusions. With competing image providers (bing_images, duckduckgo_image, yahoo_search_images) as siblings, the agent gets no signal about when Brave images is the right pick. Usage is only implied by the verb 'Search'.

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