Skip to main content
Glama

brave

by ai.smithery
OverviewDiscussionsAdmin

Image search

brave_image_search
Read-only

Performs an image search using the Brave Search API. Helpful when you need pictures of people, places, things, graphic-design ideas, or art inspiration. Counts of up to 100 are supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (max 400 characters and 50 words).
countNoNumber of results (max 100; default 50).
countryNo2-letter country code (ISO 3166-1 alpha-2). Defaults to US.
safesearchNoFilter level for adult content.
spellcheckNoWhether to spellcheck the query.
search_langNo2-letter language code for the search. Defaults to en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / count / default
      Removed value: -50
    • changedInput schema / properties / count / description
      Previous value: -"Number of results (1-200, default 50). Combine this parameter with `offset` to paginate search results."New value: +"Number of results (max 100; default 50)."
    • removedInput schema / properties / count / maximum
      Removed value: -200
    • removedInput schema / properties / count / minimum
      Removed value: -1
    • changedInput schema / properties / count / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / country / default
      Removed value: -"US"
    • changedInput schema / properties / country / description
      Previous value: -"Search query country, where the results come from. The country string is limited to 2 character country codes of supported countries."New value: +"2-letter country code (ISO 3166-1 alpha-2). Defaults to US."
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Search query (max 400 characters and 50 words).",
+  "type": "string"
+}
    • removedInput schema / properties / query
      Removed value: -{
-  "description": "The user's search query. Query cannot be empty. Limited to 400 characters and 50 words.",
-  "maxLength": 400,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / safesearch / default
      Removed value: -"strict"
    • changedInput schema / properties / safesearch / description
      Previous value: -"Filters search results for adult content. The following values are supported: 'off' - No filtering. 'strict' - Drops all adult content from search results."New value: +"Filter level for adult content."
    • changedInput schema / properties / safesearch / enum
      Previous value: -[
-  "off",
-  "strict"
-]New value: +[
+  "off",
+  "moderate",
+  "strict"
+]
    • removedInput schema / properties / search_lang / default
      Removed value: -"en"
    • changedInput schema / properties / search_lang / description
      Previous value: -"Search language preference. The 2 or more character language code for which the search results are provided."New value: +"2-letter language code for the search. Defaults to en."
    • removedInput schema / properties / spellcheck / default
      Removed value: -true
    • changedInput schema / properties / spellcheck / description
      Previous value: -"Whether to spellcheck provided query."New value: +"Whether to spellcheck the query."
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "q"
+]
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "count": {
-      "minimum": 0,
-      "type": "integer"
-    },
-    "items": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "confidence": {
-            "description": "The confidence level of the result.",
-            "enum": [
-              "low",
-              "medium",
-              "high"
-            ],
-            "type": "string"
-          },
-          "page_fetched": {
-            "format": "date-time",
-            "type": "string"
-          },
-          "properties": {
-            "additionalProperties": false,
-            "properties": {
-              "height": {
-                "exclusiveMinimum": 0,
-                "type": "integer"
-              },
-              "url": {
-                "format": "uri",
-                "type": "string"
-              },
-              "width": {
-                "exclusiveMinimum": 0,
-                "type": "integer"
-              }
-            },
-            "required": [
-              "url",
-              "width",
-              "height"
-            ],
-            "type": "object"
-          },
-          "title": {
-            "type": "string"
-          },
-          "url": {
-            "format": "uri",
-            "type": "string"
-          }
-        },
-        "required": [
-          "title",
-          "url",
-          "page_fetched",
-          "confidence",
-          "properties"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "might_be_offensive": {
-      "description": "Whether the image might be offensive.",
-      "type": "boolean"
-    },
-    "type": {
-      "const": "object",
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "items",
-    "count",
-    "might_be_offensive"
-  ],
-  "type": "object"
-}New value: +null
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Added
  7. Removed
  8. Added
  9. Removed
  10. Added
  11. Removed
  12. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / safesearch / anyOf
      Removed value: -[
-  {
-    "const": "off",
-    "type": "string"
-  },
-  {
-    "const": "strict",
-    "type": "string"
-  }
-]
    • addedInput schema / properties / safesearch / enum
      Added value: +[
+  "off",
+  "strict"
+]
    • addedInput schema / properties / safesearch / type
      Added value: +"string"
    • removedOutput schema / properties / count / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / items / items / properties / page_fetched / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"
    • removedOutput schema / properties / items / items / properties / properties / properties / height / maximum
      Removed value: -9007199254740991
    • removedOutput schema / properties / items / items / properties / properties / properties / width / maximum
      Removed value: -9007199254740991
  13. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, etc. The description adds context about maximum count (100) but does not detail response format or other behavioral traits. For a read-only tool with annotations, this is adequate but not exceptional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no fluff, front-loaded with purpose. Every sentence serves a purpose.

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 simple image search with good annotations and schema coverage, the description is sufficiently complete. It could mention output format (e.g., URLs, thumbnails) but is not necessary given the tool's simplicity.

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 coverage is 100%, so baseline is 3. The description does not add meaning beyond the schema, though it mentions 'counts of up to 100' which aligns with the count parameter.

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?

The description clearly states it performs an image search and gives examples of use cases. However, it does not explicitly differentiate from sibling tools like brave_video_search or brave_web_search, though the name implies image-specific functionality.

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 says 'Helpful when you need pictures...' which implies use cases but does not specify when not to use or mention alternatives among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All brave toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources