brave-image-mcp

search_images_batch

Search for images using multiple queries in a single call, sequentially combining results to collect images across several topics at once.

Instructions

Search for images using multiple queries in a single call. Runs queries sequentially and returns combined results. Useful for collecting images across several topics at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "queries": "<queries>"
    },
    "name": "search_images_batch"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of results per query (1–200). Default: 10.
`country`	No	2-letter country code or 'ALL'.
`queries`	Yes	Array of image search queries (max 10).
`safesearch`	No	Content filter level applied to all queries.
`spellcheck`	No	Enable spell checking on all queries.
`search_lang`	No	Language code for search results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that queries run sequentially and results are combined, which are meaningful behavioral traits. It does not discuss error handling or rate limits, but for a read-only search tool this is acceptable.

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?

The description is two sentences, front-loaded with the main action, and contains no redundant or filler content.

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?

With no output schema and moderate complexity (6 params), the description explains the core behavior but leaves gaps around return format and partial-failure behavior when multiple queries are involved. The schema covers parameter details, but the tool description could more fully describe expected outputs.

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%, with every parameter having a description. The tool description adds no parameter-level detail beyond what the schema already provides, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as searching for images using multiple queries in a single call, and explicitly distinguishes it from single-query search by emphasizing batch behavior and combined results.

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

Usage Guidelines4/5

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

It states the tool is useful for collecting images across several topics at once, implying batch use. However, it does not explicitly mention when not to use it or directly compare with the sibling search_images tool.

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

Deploy Server