When to use:
    - General web searches for information, facts, or current topics
    - Location-based queries (restaurants, businesses, points of interest)
    - News searches for recent events or breaking stories
    - Finding videos, discussions, or FAQ content
    - Research requiring diverse result types (web pages, images, reviews, etc.)

Returns a JSON list of web results with title, description, and URL.

When the "results_filter" parameter is empty, JSON results may also contain FAQ, Discussions, News, and Video results.

Returns detailed information including:
    - Business names and addresses
    - Ratings and review counts
    - Phone numbers and opening hours

Use this when the query implies 'near me', 'in my area', or mentions specific locations (e.g., 'in San Francisco'). This tool automatically falls back to brave_web_search if no local results are found.

When to use:
    - When you need to find videos related to a specific topic, keyword, or query.
    - Useful for discovering video content, getting video metadata, or finding videos from specific creators/publishers.

Returns a JSON list of video-related results with title, url, description, duration, and thumbnail_url.

Performs an image search using the Brave Search API. Helpful for when you need pictures of people, places, things, graphic design ideas, art inspiration, and more. When relaying results in a markdown environment, it may be helpful to include images in the results (e.g., ![image.title](image.properties.url)).

When to use:
    - Finding recent news articles on specific topics
    - Getting breaking news updates
    - Researching current events or trending stories
    - Gathering news sources and headlines for analysis

Returns a JSON list of news-related results with title, url, and description. Some results may contain snippets of text from the article.

When relaying results in markdown-supporting environments, always cite sources with hyperlinks.

Examples:
    - "According to [Reuters](https://www.reuters.com/technology/china-bans/), China bans uncertified and recalled power banks on planes".
    - "The [New York Times](https://www.nytimes.com/2025/06/27/us/technology/ev-sales.html) reports that Tesla's EV sales have increased by 20%".
    - "According to [BBC News](https://www.bbc.com/news/world-europe-65910000), the UK government has announced a new policy to support renewable energy".

When to use:

- When you need a concise overview of complex topics from multiple sources
- For quick fact-checking or getting key points without reading full articles
- When providing users with summarized information that synthesizes various perspectives
- For research tasks requiring distilled information from web searches

Returns a text summary that consolidates information from the search results. Optional features include inline references to source URLs and additional entity information.

Requirements: Must first perform a web search using brave_web_search with summary=true parameter. Requires a Pro AI subscription to access the summarizer functionality.

When to use:
    - Grounding answers in fresh, relevant web content (RAG)
    - Giving an AI agent ready-to-use page content from a single search call
    - Question answering and fact-checking against current sources
    - Gathering source material for research without manually fetching pages
    - When you need the contents of pages, not just titles, descriptions, and URLs

When relaying results in markdown-supporting environments, cite the source URLs from the "sources" map.

When to use:
    - POIs near coordinates or a named area (e.g. "coffee shops in Paris") -> 'results', each with structured business data (postal address, hours, contact, ratings, photos, categories, timezone).
    - Browsing general POIs (omit 'query'; supply 'latitude'+'longitude' or 'location').
    - Disambiguating a bare city name (e.g. "springfield") -> 'cities'.
    - Resolving a specific address (e.g. "350 5th avenue" with NYC coords) -> 'addresses' (often plus 'streets').
    - Looking up a street by name (e.g. "michigan avenue" with Chicago coords) -> 'streets'.

Inputs:
    - Anchor the search via 'latitude'+'longitude' or 'location' (or both). With neither, 'query' is required.
    - 'addresses' / 'streets' only surface when the query is address-/street-shaped AND geographically anchored.
    - 'location' format: US -- '<city> <state> <country>' (e.g. 'san francisco ca united states'); non-US -- '<city> <country>' (e.g. 'tokyo japan'). Capitalization and commas don't matter.
    - 'count' caps results (max 50, default 20). 'radius' (meters) biases toward closer results; it does NOT hard-limit the search area.